Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

Status No Status
Categories Notifications
Created by Guest
Created on Aug 20, 2022

Include Creation date in event frame properties for Notifications

We see issues where notifications appear to be delivered late but then find the event frame was created at a later time than the actual event because of connectivity issues. Having the creation date of the event frame exposed for a notification would be helpful in informing of such issues.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    In the case of a recalculation, what would you expect the EF creation date be?
  • Guest
    Reply
    |
    Aug 20, 2022
    This is an old thread, but I'll add my 2 cents anyway. Creation date of the EF should be the actual time of EF creation. In the case of a backfill, this time would be the time the EF was backfilled. If I had access to this "creation date" I would be able to compare the creation date to the start date and put my own logic in to control when and/or if a notification should get sent. I feel like this solves my "don't send a notification on a backfill" case too. Although I suppose that also means I need to be able to do more robust logic comparisons for a notification trigger than "Equals" and "Not Equals"