It would be useful to have the possibility to include EFs in a Time Based Template.

For example:

- if downtime events are recorded as Event Frames, I would like to report on all the downtime EFs occurred in the last month (for example), including acknowledges and annotations.
- Using PI Connector for Siemens Simatic PCS7, conditions end-up in PI Event Frames accompanied with a related set of static and dynamic attributes. Having the possibility of including Conditions EFs in a time based report could be useful.

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 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.

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.

As a PI User, if I comment and approve a report in RTReports, I would like to have the ability to view those comments approvals, etc in other PI visualization tools like DataLink and PI Vision. 

If Comments, approvals, esigs could be attached to the associated EF and stored in the AF database, this data set would be more easily consumed by others in my organisation.

As an RTReports administrator I would like to have the ability to incorporate comments and annotations that users attach to Event Frames .  For example, I would like generate a notification report for a unit over a period of time - PI notifications now stores acknowledgments, comments, approvals and I think severity in the AF database.  when generating my notification report I would like to incorporate this data into my 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.

Provide the ability to change the position (bottom/top/left/right and so on) of the Approvals Table in the Report. Currently, it always shows up on the top of the report.

As an RtReports User, I want to dynamically link to RtReports Generator to create Reports. At the same time, I want to specify the time zone context of the report dynamically. For instance:
..rtreports/WebPages/ReportTemplate.aspx?ReportName=TestReport&TZ=Singapore+Standard+Time&..&..&..

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

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.

For journal actions, there are performance equations that require time inputs such as TagMin, TagAvg.

Currently, to use those functions, you need to hardcode the start and end times using relative time or exact timestamps. 

This is not super useful for batches as everything should be related to the batch context.

It would be nice to pass on batch context values (ie. Start Time and End Time) to these performance equations

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)

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.

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).