When a backfill or "recapture events" option is selected for Event Frames, give the user an option to "Save Annotations" for that specific event frame. Right now, we use Event Frames to copy in Reason Codes and Comments (that are logged as annotations) so we are limited in backfill or recapturing the data if historical data changes.

Changing from Expression to Rollup by mistake will erase the Expression configuration in PI System Explorer. Add a warning message regarding this.

On PI AF in Library on Element Templates - Analysis Templates, the evaluate button should be able to evaluate logic at a previous point in time as well as the current time. This would allow better visibility over how logic performs for periods of time in the past, and will be better for debugging logic.

When input PI Tags are referenced in PI Vision 2020+ calculations, they do not automatically detect PI Tag name changes. For users with a lot of calculations, this can be extremely problematic in the event of a PI Tag name change. In the event of a name change, the following error is produced: [-12301] Performance Equation parsing error. Possibly updating the PE scheduler to reference the PointID instead would be beneficial.

When doing a fresh installation of AF Server, and either the "Validate SQL Connection" option or other Software like PI Notifications, RTQP Engine are selected, the installation cannot be started when the AF SQL Database is not called "PIFD".
As the Installer is looking for a SQL Database with a hardcoded name, it throws one of the errors described here:

https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000034342

Possible workarounds
1) Further specify the error messages so that the user exactly knows what is causing this error message.
2) Add an option in the installer to look for a SQL Database named differently

Found out that the decimal points is up to 3 decimal only. Can you improve the PI Integrator that has its own decimal places? and also not depending on the AF for adjusting the display digits?

Thanks

The feature introduced in 2018 SP2 to manually synchronize digital state sets with AF enumeration sets has a limitation where state sets with duplicated names aren't imported correctly into AF. This is due to the current design of AF enumeration sets that don't allow duplicated names for enumeration values. It would be nice if AF enumeration sets supported multiple values with the same name as it is supported in digital state sets in the Data Archive.

When troubleshooting intermittent issues, using AFGetTrace may be problematic as the trace can consume quite a bit of disk space, and setting a maximum file size will cause the trace to stop once the file is full. Without knowledge of when the issue will reoccur, we are stuck either risking filling up the disk and having a huge trace file to analyze, or set a max file size and possibly miss the issue.

When shrinking the tabs in the lower left pane of PI System Explorer (Elements, Event Frames, Library, etc.), the tabs do not shrink if shrinking by one. If shrinking by two, it only shrinks by 1, etc. These tabs should shrink accordingly.

When connecting Redis database via DSN we get error. As interface is ASCII and Redis is Unicode. Please add the unicode support for RDBMS interface.

A web service endpoint, for instance ServiceNow, may response with useful information to a notificate, like a ticket number. There should be a way to associate that information with the event frame that triggered the notification.

At the moment i have to conifgure attributes like description or uom in PI Tags and also in the corresponding AF attribute. it would be great if i could use substitution paramertes like point.uom or point.descriptor in PI AF to fill configure Attribute parameters.

It would be very useful if an "outage" for PI Notifications could be scheduled. We often start or finish maintenance well outside of work hours, and the flood of PI Notifications can annoy users who are not on site.
Ideally we could set an outage for PI Notification emails during a set advance time (eg between 5 and 8am on the 19th June 2021).

There are Modus supporting devices that feature 32bit single registers (e.g ROC800-Series). PI Interface for Modbus should be updated to have support to output to these 4byte (32bit) registers.
Currently PI Interface for Modbus only has support for output to single 2bype registers or output to multiple 2byte registers to store 32bit data. There is a need to have the interface support output to single 32bit registers.
Example device manual: https://www.emerson.com/documents/automation/roclink-800-configuration-software-user-manual-for-roc800-series-en-132340.pdf

Currently, in PI Builder there is a hard limit on the number of columns that can be selected (it is set to 1023 columns). It makes it hard to work with templates that have over 1020 attributes configured and limits the configuration capabilities.