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.

RtReports Editor allows the generation of a new version of a template from a version different from the current one, and no warnings appear.

This was the root cause for a serious issue.
A warning message would be very usefull.

A confirmation message on deletion would be very usefull. At the moment the deletion is "too easy" and there is not "undo" button.

The "undo" button would be usefull for any action as well.

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

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

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.

Utilize Report Parameters to select things like Asset Names, Asset Templates, and Root Paths in Reports that use Asset Context Templates.

Example use case: A customer has 100 units based on the same AF template and would like their users to be able to select a specific, desired unit from a drop-down list (i.e., utilizing a report parameter) in the RtReports Generator to run a time-based report against. They would need to configure an Asset Context Template in the RtReports Editor, with the AF Template specified, and the Asset Name set as a report parameter.

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

Default filter for all users every time they log into the application. The RtReports generator search page requires a user to enter the filter every time they log into the application. This is especially burdensome as the users are logged out after a minute or two of inactivity.

Allow values to be passed into the RtReports Generator URL in order to modify the default Start Time, End Time, BatchID and other parameters.

Some customers are using the same RtReports Server to connect to both PI Data Archives (for batches) and Asset Framework Servers (for Event Frames) since they are using both at the same time. They'd like to be able to store both DA and AF/Database in the Generator, so there's no need to click around selecting them.

Customer wants to use a parsed value in a Trendobject. He has an an attribute in AF with several columns. He wants to use one of the values of the pipes and re-insert it in Rtreport editor as a Trendobject. At the moment, using a parsed string tag in a trend cannot be done ad-hoc in RtReports. A PI tag or AF attribute is required, therefore customer should have an extra attribute. RtReports needs a Trend result to be used as the Trend object.
The request is to be able to use a parsed value in a Trendobject

Following the "Parse String Tag Using an AF Attribute as a Filter" KCS is a very complex setup to filter Strings based on AF Attribute values.

We would like to see the filter functionality enhanced to allow filtering based on an AF Attribute Value.

Link to current workaround: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000025025

Currently, when an upgrade or a migration of the PI Server is performed, in order to carry over the comments and verifications for time-based reports the only option is to name the new PI Server the same name as the old PI Server.

Fixing this would be a great benefit for users that need to have comments and verifications visible on the reports after complex migrations, in which the PI Server name can't be kept the same.