Customer would like a specific Notification to use a 24 hour time format, while all other Notifications use the 12 hour time format.

For Example: Notifications A sends out emails in a 24 hour time format. All other notifications sends out emails in a 12 hour time format.

Currently it is possible to change all Notification time formats but it is not possible to change individual Notification time formats.

I believe the rather complex process of migrating from the legacy version of PI Notifications to PI Notification Rules and the new paradigm of how they operate deserves an online course in how to migrate, set up, configure, test and improve your new PI Notification Rules.

When setting a notification's trigger criteria and specifying the "Event Frame Search" option, give the user more options for triggering on Attribute Values.

Current options: Equal, Not Equal
Suggestions: Greater Than, Less Than, Greater Than Or Equal, etc.

Additionally, allow the user to specify AND/OR clauses between multiple Attribute Value triggering criteria. Currently, this seems to be an implicit AND only.

As a notification user, I want to receive a phone call when my equipment fails and I want the message I had configured in the format read out to me.

As a notification user I want to see a table of all the attributes and its values on the target element in my email, furthermore when I add or remove attributes I want to see it automagically updated in my email without me having to reconfigure the table in my format.  

As a PI Administrator I need PI Notifications to support custom headers for SOAP web service end points. Some external systems require specific headers and currently it is only possible to customize headers for REST end points. As an example of an external system, to utilize Maximo security a custom header must be included.

Enable users to drag and drop multiple contacts into the subscribers pane, rather than selecting each contact one at a time.

Put Format Painter into notification message formatting, as in Word.
It takes a lot of time to set separate format of each content.

The Notification Webservice only authenticates HTTP header for now and not SOAP header.

Currently, PI System Explorer's Notifications Message Editor does not allow the user to change the display text for a hyperlink that links to a File. There are some workarounds (such as using PI Builder to edit the XAML directly), but it would be nice to have this functionality built-in.

As a PI System Administrator, I want to set the Resend Interval at an attribute so I do not have to enter every time at the notification and take some time to change it.

From time to time we have different priority levels on our equipment that needs more monitoring due to unwanted conditions, especially if there might be something going wrong. Doing it directly at attributes would save a lot of time.

When a trigger condition is satisfied run an executable. This might be possible using Custom Delivery Channel but Custom Delivery Channels are no longer supported in PI Notifications 2.x

The Notifications rules email format should include backfilling history and details of its respective event frame in the content options. The backfilling content can include:
- Completed Time
- Start Time
- End Time
- Last Evaluation
- Events Processed

See the screenshot attached to see an example of the dialog that appears when hovering over the event frame or analysis. This would provide information to the users to know if these were recalculated.

Allow free-form JSON construction. Maybe not replace the simple JSON guide that is the only entry form now, but free-form would allow the kind of flexibility that would empower the user.

This would allow a single template to be used, rather than the workaround to manually override the template for every individual sensor configured, resulting in hundreds of template copies in which only the "Path" field is edited

Allow for additional authentication types to be added for web service delivery endpoints. Currently, the only available options are Windows, Anonymous, and Basic.

When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to allow escaping it with a backslash or even better (IMHO) to use the JSONPath way to solve this: being able to specify arbitrary property names putting them between brackets and single quotes: ['prop.erty'].

Currently there are options in a radio button configuration under "Choose when to be notified if child event frames are created for multiple trigger conditions" but there isn't a "do not notify for child event frames" option.

Please add the "Do not notify for child event frames" option.