Thanks for implementing https://feedback.osisoft.com/forums/555148-pi-server/suggestions/32874406-notification-e-mail-delivery-channel-to-accept-mul

I would like to see "CC" and "BCC" in addition to "To".

At out company the receipients of "To" should do the necessary work involved with the notification and the recipients of "CC" (and "BCC") should only be informed.

It would be nice if ";" (semicolon) would also be accepted as a separator betweeen multiple email addresses. I think MS Outlook takes the regional list separator.
Maybe it would be best to provide a tooltip in all email fields to show this option.

Allow for PI AF templates to be version controlled. Include the ability to revert to previous template version, or continue to use old versions for specific elements. This will reduce the risk of deployment and improve change/release management process.

It would be helpful if you could search by Element Category or Element Description when searching for Analyses in PSE. My setup is 5 templates (CHW, Water, HW, Electric, Steam), each of which have accounts that can come from 5 different sources (selectable by element category). I can't filter by both commodity type AND source, I can only do Commodity type using the "Template" criteria option, as the "Category" and "Description" search criteria options relate to Analyses, not to elements. This severely limits the functionality of the search feature for me.

Allow a default value to be specified for rollup analysis. This value would be used when the rollup cannot find any matching attributes, thereby eliminating a lot of rollup analysis errors and Calc Failed values from being written.

Currently, when you remove a template from an Element in PI System Explorer, you'll remove all existing attributes from the Element.

There should be a functionality in PI System Explorer to remove the template without making changes to the attributes for the element.

Currently, the only workaround is to use PI Builder to remove the template without removing the Attributes associated with said Element.

Feature of Notifications 2012 that was not carried forward - big mistake.

Need the ability to customize the sender email on notifications.  Makes it easier for users to configure email rules to take actions such as file in certain folders, forward, etc.  Also - with iPhone VIP setting, can set up phone to alert differently for critical notifications.

Huge swing and miss...

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 a PI Administrator of a PI System with complex security requirements, I need to set up different default permissions for various users so they can create tags that automatically have the proper security instead of having to rely on a process/procedure to correct security after the tags are built.

Have a way to manually (or automatically via another calculation/analytic) put the status of an asset/equipment into an offline/maintenance mode that has the effect of turning any analyses and notifications for that asset off.

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.

It is difficult to find all the analyses from template to backfill/recalculate after making changes in Analysis Template.  Currently one has to navigate to the Management plug-in, do some sort of search/filter, then queue the analyses.  This is a multi-step process.  Consider providing a better user experience.

It would be useful to trigger event-triggered rollup analyses upon adding new children. Currently rollup analyses are only triggered when rollup attributes are updated (and not triggered when rollup attributes are added). This would be particularly useful in cases where the rollup analysis is dependent upon the number of children such as an average. The current implementation results in misleading values when child elements are added or removed.

Analyses can suffer from bad calculations due to bad events for a tag, such as system digital state events returned for a numerical tag.

Although BadVal() can be implemented to avoid using bad events in these analyses, they add another layer of complexity the expression.

The addition of a "Use Good Data" only option in the analysis tab in PSE that applies BadVal handling on top of an analysis would help simplify expressions.

When you have thousands of tags in your Data Archive, you need to know wich tags are beign used and witch don't. It would be very usefull to have some diagnostic that shows wich tags are being cosumed more and from wich client.

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.