Provide additional Time Format setting for Duration, other than “xx days xx hours xx minutes xx seconds”

Provide more power and flexibility to who approves reports. Currently, you can set the order of approvals.

It would be nice to be able to determine who or which approval track a report goes to or undertakes based on the results of the batch (IE which alarms were tripped during the batch)

As an report designer, I would like to be able to choose the position of the legend on Trends.

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.

Provide the possability to send notifications based on the approval-cycle status of the report.
For example: In a "two-steps" approval cycle, send a notification to the final approval group when the first group approved the report.

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.

I would like to be able to access RtReports review data programmatically (e.g. via ODBC) so we can track which reports are ready to be reviewed by Manufacturing/QA.
It would also allow us to monitor the time taken to complete reviews and help drove improvements in lot release times.

Currently, non-recurring time based RtReports do not properly resolve the "Generated By" report info parameter. Instead of displaying the user, these printed reports display the text "Generated By".

On the other hand, batch reports and officially printed recurring time based reports resolve this parameter properly.

In order to provide a consistent behavior, non-recurring time based reports should be able to make use of this report feature.

Provide the ability to control the font or position of the Official Print in the Editor and Generator.

Provide a native 64-bit version of the RtReports Server.

Provide the ability to export report template list from RtReports Editor.

As a RtReports user, I would like the context level I select in the RtReports Generator to be the context used in the generated report. For example, if I click on a PIUnitBatch I would expect to see only data from within the start and end time of the PIUnitBatch. The current behavior is to crawl up to the top level of the batch structure and use that for the context of the generated report.

Customer wants to be able to export a report list to Excel.  In the RtReports Editor you can generate a list of reports in the Report Properties window but it is not possible to export or copy.

Enhancement Request:  Allow the ability to either export a CSV or copy the contents of the Report Properties window

Provide the ability to sort phase parameters by entry time, rather parameter types.

Provide the ability to tune the RtReports Server to get more report generation throughput.

Make user's preference of View (Batch, Equipment etc.) in the RtReports Generator a user-specific setting

Provide the ability to show a Time Zone Information with date time on a Report.
(Feedback captured)

The current RtReports does not have any "next line" control character/object that customer is using Text object: </br> which is not recommended by OSIsoft developer

As an RtReports administrator, I would like to set my reports to only require the review cycle to be completed if the batch data is flagged as questionable. Otherwise, no manual review should be required.

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.