Provide the ability to automatically run a report after a batch completes.

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)

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

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.

we are designing our AF structure for a new customer and they would like to use the RTReporting capabilities later on so I want to make sure we design for success.. Things like for example make the “Limits” option in AF be available to pull into RTReports

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.

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 ability to control the font or position of the Official Print in the Editor and Generator.

Support creating a time based unit report so common AF attributes can be printed that are defined for common Asset Classes

When creating PDF reports in 3.3 AdobePDF would allow for password protection as one of the printing options. Since RtReports 4.0 no longer uses AdobePDF, the option to print with password protection should be allowed.

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.

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

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

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

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

Provide the ability to run a report based on schedule.

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.

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.

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

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.