Feature Ideas

Right now there is no versioning of reports in the library, so if a mistake is made on an existing report there is no way to recover the prior version without database restores. Allow the versioning of reports so a user can go back to a prior version if needed.

Be able to migrate a report or dashboard from one system, such as a development system, into another Yurbi system without the need for API programming/scripting.

Allow users that know how to write SQL queries or already have SQL queries generated to be able to leverage those in the Yurbi report building process. Please leave feedback on how you would use this feature and where you would want it. For example: Creation of a Yurbi App dynamically from a SQL query. This would limit access to Architect level users and continue to leverage the Yurbi App which is the hub of all security and Builder Access. Allow Builder to create reports directly from SQL queries. This would potentially by-pass Yurbi security and allow anyone with builder access to run any query they wanted, Feedback on your desire and use case for this needed.

Currently to enable fast cache the admin must edit each user individually to turn on the feature and hit save. While there is an API/Server script to do enable multiple users at a time, it would be nice to have a way in the interface to multi-select or mass update the FastCache setting the way you can currently mass edit the Groups and App assignments.

When you have multiple values that you wish to compare to a baseline, provide an easier way to calculate the relative performance between columns.

Currently, there are a few way to generate a data comparison dataset but it requires more effort than other report types. Since this is a common requirement, provide a simpler way to add a date driven column in the report dataset.

Add the ability to add a trend line to a chart the way that Microsoft Excel provides.

When you set a filter on a dashboard, it updates the KPI but doesn't apply those filters to the sparkline display in the KPI.

Ability to leverage a highly formatted Microsoft Word template with tags that match to data stored in a dataset and have the export capability to create and export multiple pre-filled templates.

Add a setting to the fastcache so that caches are only built for users that have actively logged in within a certain period, or have logged in so many times within a certain period. This will reduce the total number of caches built and maintained and make the system more optimized.

Currently only admins are able to reset a users password if they forget it. Enable a forgotten password feature for agents and builders.

Currently the report builder has full control of what report data can be shared as a Guest View or Public View Document. This feature is to include the Guest View or anonymous user as a reserved user type so that it can have App Shield policies attached. So regardless of what the Builder creates, the organization can set a policy on what data limits are. A secondary benefit of this feature will be to allow dashboard caching to apply to anonymous dashboards.

Currently only the actual user can add a dashboard or report to their favorites list. Developers can use the API to do this, but for normal admins provisioning users, they must log into each user account to set up the favorite/assigned dashboard and reports. Would be nice to have a way that builders or admins can assign on the user's behalf.

Add the ability to have chart elements change color if they are over or under a specific threshold.

Allow the arranging of saved fields in the same way you can re-organize and order your favorited dashboards.