Add the capability to perform scheduled backfills for a specific time frame, for analyses created on PI System Explorer.

It would be great to have the ability to hide the Event Frame End Time in the Notification Email when the notification first triggers.
At this time, and End Time of 12/31/9999 11:59:59 PM Central Standard Time (GMT-06:00:00) is displayed even though an event is not closed.
Note: in this case notifications have been set up to send at Event Start and End Time.

As an engineer I need the option to not capture values for event frames generation so that if I have out-of-order events, I don't have to recapture the values.

Note: This was previously Enhancement 114349.

Provide the capability to apply compression on uncompressed data, aka recompress using offline archive utility.  See work item 6944OSI8.

Currently, in PSE there is no way to display attribute values greater than or equal to 1000 with commas for the thousands separators. Ex: 1,234,456 instead of 123456. This option exists in other PI Clients (i.e. PI Vision) and should be available in all PI Clients.

Using the Max Rollup function - I would like to know which element provided the maximum value and output this as well so I can historize the information.

We've several PI servers and AF servers where same products are running, so we need the ability to search Event Frames across our AF databases to compare production performance. This search ability should be available in all clients; PI Vision, DataLink etc.

We have hundreds of mappings/trusts in SMT and there's no way to search them (apart from exporting it all to Excel, and searching there, then going back to SMT to make necessary changes - not user friendly). There needs to be a basic search bar at the top of that panel, and it should search all fields (except server and collective) in whatever tab has focus (mappings or trusts). 

Ability to link Event Frames coming in from different sources (batch & mes interfaces, EFgen, PI Analytics, custom, etc.) together based on rules and monitoring an EF attribute SO THAT it's easier to associate time frame context and data that is related together but come from different sources.

As an AF Administrator, I want to configure an Analysis Template for Event Frames with a True For parameter that would have it's value stored in an AF Attribute (configuration item). The use case is that elements built from the template will have Event Frames that will require a different True For value. I would like to have the analysis both base off a template and with the possibility of having different True For values. It would also be nice to have a True For parameter for the End Time. This is already a request:

https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17648182-event-frame-end-trigger-time-true-functionality

Currently, if an event frame generation analysis is renamed, all notifications rules that use it will display an error message, saying that the event frame generation analysis might have been renamed or deleted.

This message is fine for deletions, but it would be much more user-friendly if the notification rules were to automatically update to reflect the rename of the event frame generation analysis.

Formula data references do not support string value type attributes (e.g. if stringattribute="Yes" then "X" else "Y"). One workaround is to create an analysis on the element template with the same logic mapped to an attribute on the element template. In certain cases, however, an analysis will not work.

For example, for an event frame with manually-entered string data individual to each event frame that then determines the value of another event frame attribute based on IF/THEN logic), we need this value to be calculated per event frame and not on the element.

I want to run the Auditviewer function as a unprivileged remote user, moving away from the current requirement to run as a local user on the PI Data Archive Server.  This is so I can minimize security risk associated with local user access on a Windows server.

While no customers have asked for this directly, I have seen many customers ask how to check a tag for being stale. The solution to date assumes all tags have the same staleness timeout, which really is not the case most of the time.

This new "StaleTimeout" point attribute would be a duration (time span) customizable for each tag. There could also be a new PIPoint property called "IsStale" which could bounce the current value's timestamp off the "StaleTimeout".

As a user of Asset Analytics I would like to have more flexibility in including elements in my rollup calculation so that I would not need to build large hierarchies just for the purpose of rollup analyses.

Allow a different naming pattern for the child event frames. End result would have the long, uniquely named EFs in the Parent EF as usual, but the Child EFs could have a simplified name, like the level of an alarm that is pulled from an attribute value (capable as of AF 2017 R2).

I have a scenario where I would like that a certain Notification Rule, set for an Event Frame analysis (EF1), allows to return the value of an EF attribute belonging to a different Event Frame (EF2).

On this scenario, the EF2 is triggered and finishes inside the time period of EF1.

I would like to have the possibility that when EF1 is triggered the notification rules allow to find the value of the attribute belonging to EF2.