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

Follow all notifications status & be able to resend a notification

When a notification is not sent, it's very difficult to follow which notification has been sent or not. In case where the notification has'nt been sent, have the possibility to send manually the notification.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Is this a troubleshooting mechanism for Notifications? Have you looked into the Notification history (2012 or earlier) or the Event Frame annotations (2016 R2 or later)? It wouldn't seem productive to provide a list of failed Notification sends (if it indeed failed) as if it can record the failure, it should have just sent. So I'm curious if this is a deficiency in the product functionality (in which case a TS case might be best to address it) or a deficiency in the product feature set. As for manually sending the Notification, I'm also curious what this would be. Are you saying that the Event Frame is already created, but you want to send out a Notification based on it at any given time? Is this to address the failure of sending or just as a manual resend based on an administrator's preferences?
  • Guest
    Reply
    |
    Aug 20, 2022
    For some clarification: the customer is calling a webservice from Notifications. If the webservice is down for several hours and then comes back up, she would like the option to be able to manually resend all Notifications that have a SendStatus of Failed. One workaround is to configure the Retry Interval and Maximum Retries for the webservice delivery endpoint, but in the case of the webservice being down for several hours this may not be practical. They would either need a large Retry Interval (which could delay notifications from being sent in the case that the send error occurred due to a temporary issue with the webservice) or large number for Maximum Retries (which could put unnecessary load on the Notifications server).
  • Guest
    Reply
    |
    Aug 20, 2022
    Hi Laura, I'm align with your comment. We use a webservice notification. If the called webservice is down for 1 hour (for example), we should be able to resend all failded notifications.