In AF please provide a way to suppress time zone and/or to format the timestamp in AF Events, particularity, Notifications. For example, in the message format in e-mail notification I do not need to indicate the time zone it was triggered in.
Please make this available in the AF SDK as well as in PI System Explorer.

Add the triggers to SQC rules to reset or hold the SQC rule. When monitoring a periodic or batch based process, a user needs to be able to hold the SQC rule or put that rule in a hold state until the process resumes. Without this feature, virtually all violations to the SQC rules are caused by the downtime periods - not the steady state process users are really intending to monitor

As a PI Administrator with a test PI Server, I need to be able to easily promote configurations from our test environment to our production environment. Currently this is extremely difficult and a very manual process.

As an end user, I would like to be able to change the timezone referenced in PI System Exporer from client timezone to server timezone. Something similar to the "PI Data Archive Time Zone"  setting found in PI DataLink would be helpful.

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.

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

Ability to scale event frames to support hundreds of millions of EFs per year.

It would be nice to have the ability to drag and drop the value at end time of  an attribute in the message format of a Notification. We can do this with the value at start time and the value at send time, but not the value at end time. There are some ways to workaround this, but it would be nice to have it as a drag and drop option.

As an AF administrator, I  would like to send in an attachment of a Notification files that are specified by file path in AF attributes. I currently do this by specifying the value at start time of an AF attribute that contains the changing file paths,  in the body of the email. I would like to have this as an attachment instead.

A feature to review the changes that will be made when importing AF templates that have been exported from a lower environment.

Example.
Make changes to element/attribute/archive templates in dev.  Export library to XML.  Compare export to QA templates and provide a report on what all will change to be reviewed before importing.  If it has only the changes you intend to promote, then you can go ahead and import.

Als a PI admin I want to have the option to stop/end a EF after a given time. This helps to trigger and track onetime events as for example taking a reactor sample.

Would like ability to use substitution parameters in attribute template names.  Using PI-SNMP for Linux file partition data. We need to know the storage index# in AF since they vary server to server.  Want to provide users doing searches the actual partition name and the data for them, instead of using Storage Index name attribute (tag value) to determine which is which.

see https://pisquare.osisoft.com/message/77201-substitution-parameter-in-attribute-name-of-template?q=substitution parameters in attribute

For recursive Analyses such as below :
PrevVal(tagA,'*') + 'TagB' → output : tagA

When the PI Analysis Service is down (or the node needs to be restarted), the current calculation needs to be halted until the Backfilling reaches up to the start up time. Or else the value will not be as expected.

As an AF user, I would like to be able to store a tag’s instrument tag value in an attribute so that it can be used in the content of a Notification. For example, notifying someone on data from a PING interface where the instrumenttag property holds the IP Address.

I am able to create an AF analysis to store a tag’s description in an attribute using the TagDesc PE function, but there is no similar PE function to pull in a tag’s instrument tag.

As an user, I want to be able to treat event frame like time series data, such as number of active event frames, sum of an attribute, so that I can continuously monitor the evolution of event frames over time.

When a failover occur or at service startup, ALL analysis configured for backfilling executes based on the last configured backfill/recalculate timerange.

There is actually no feature to manually remove a configured backfill on a specific analysis.