AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Robert Lyon
Created on Aug 7, 2024

RELATED IDEAS

Validate Dynamic Endpoints config for notifications with new Attribute Data Reference Type

Dynamic endpoints with comma separated email addresses are the preferred method for addressing notification recipients. They allow all recipients to see which other recipients have received the notification.

The downside is any syntax error (e.g. typing a semi colon rather than a comma) invalidates the whole list, meaning that any updates to the recipient list are risky and need to be tested.

Some basic level of validation and formatting in the attribute data reference would be very handy.

I would imagine it might work in some ways like the URI builder dialog and in some ways like the array type value dialog.

  • Attach files
  • Brent Bregenzer
    Aug 6, 2025

    Maybe another option would be for the Subscriber UI to validate the endpoint config when it is added as a subscriber. I've seen cases where the attribute template linked to the dynamic endpoint is configured without a value, so that when users create new elements/notification rules and forget to add a value to the email address attribute, the notification rule triggers but no email is sent due to missing addresses. This is only caught when someone notices by looking at the data that a email should have been sent but was not received or they dig into the Notifications logs on the machine where the service lives and find an error like: Send to Dynamic Notification Email Address completed with result: Error: SMTP:NoToEmail. It would be better if errors due to empty lists or incorrect syntax (e.g., using another delimiter other than commas) were bubbled up in PSE where they are more visible.

    Reply