RtReports
Welcome to the RtReports feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.
Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.
- NOTE: for bugs, please report to OSIsoft Tech Support at https://techsupport.osisoft.com/My-Support/My-Cases/New/ rather than entering them on this site.
- NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.
-
Duration Time Format
Provide additional Time Format setting for Duration, other than xx days xx hours xx minutes xx seconds
6 votes -
Enable sorting RTReports Unit Classes alphabetically
Users may have potentially dozens of units per unit class with similar naming structures, so picking through all of these units is difficult without sorting. Since this is not configurable through the MDB, users would have to manually remove all units and re-add them in alphabetical order each time they add a unit to a class.
It would be handy to enable sorting this list, perhaps by clicking the "Units" header or otherwise.
5 votes -
Ability to delete "released" reports for demo or testing purposes
As the report designer and/or integrator, I would like the ability to delete “released” reports used for demo/testing purposes. Specifically, when having to test how the official print looked, or e-signature capability, or to show the customer how those items worked. Without that utility, testing “released” functionality is a lot harder.
4 votes -
Allow the user to control the font and position of the Official Print
Provide the ability to control the font or position of the Official Print in the Editor and Generator.
4 votes -
Time based unit aliased reporting
Support creating a time based unit report so common AF attributes can be printed that are defined for common Asset Classes
4 votes -
Improve the user experience of the "Report Edit" window
When editing the report Criteria in RtReports, editing the text fields leaves the "OK" button grayed out. In the attached screenshot, the user has edited the "Recipe" criteria field and then clicked into the "Product" criteria field. The "OK" button remains grayed out. The same behavior also exists if you use the Tab key to change fields.
Currently, the user must hit the Enter key in order to have the changes picked up, which enables the "OK" button. This can be confusing, especially for new users that do not know of this requirement.
3 votes -
Be able to sort phase parameters by entry time, rather parameter types.
Provide the ability to sort phase parameters by entry time, rather parameter types.
3 votes -
Export report template list from RtReports Editor
Provide the ability to export report template list from RtReports Editor.
3 votes -
Be able to combine multiple tags and outputs into one alarm and event table, sorted by time.
Provide the ability to combine different alarm and events into one table, sorted by time.
2 votes -
Auditing changes between report versions
Provide a tool for auditing changes between different Report Template versions
2 votes -
2 votes
-
Format template design wizard
Provide the ability to use a wizard to create report formats quickly, without using the report format template editor
2 votes -
Support XY trends
Provide the ability to correlate two tags by trending both tags in an XY type report
2 votes -
Auto save of templates
In the Editor, automatically save off the XML for the templates to some temporary location (e.g. ProgramData) and keep several of these backups (kind of like the ICU does with REM lines in the batch files) in case they need to recover an older “version” they didn’t mean to foul up.
1 vote -
Prevent the accidental deletion of report template versions
When managing reports (for deletion), add the capability to sort the report templates listed by name/version. I personally have accidentally deleted an older version of a template because there was no sort (the older version was towards the top and I wasn’t paying attention – should have actually deleted a version that was towards the bottom of the list).
1 vote -
Provide SQL lookups for limit reporting.
Provide the ability to use SQL Table lookups to do limit reporting.
1 vote -
Support intelligent mapping of bad data quality to readable text.
Provide the ability to map "bad data" to a readable text for reporting.
1 vote -
Display the logged in Windows user and their associated PI Identity in the RtReports Editor.
Provide the ability to display the logged in Windows user and their associated PI Identity in the RtReports Editor, before opening a report.
1 vote -
Support Werum batches
Provide the ability to use Werum Inteface created event frames for batch reporting
1 vote -
Comments on report template version
Provide the ability to comment on the report template version.
1 vote
- Don't see your idea?