PI Server

Welcome to the PI Server feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Web Service Configuration - Dynamic "Path" for the JSON Body

    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

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  2. Setting to send email notification to all subscribers on one email

    I believe this has been requested before by someone but I can't find it so I am submitting a new feedback/request. It would be very useful if there was a setting for PI Notifications that would allow for sending emails to all subscribers on a notification rule in a single email instead of sending individual emails to each subscriber. For example, if there was a setting that would allow sending one email for a notification rule with all subscribers on the "TO" line that would allow users on the email notification to see who else received the alert and provide…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow multiple Notification Message Formats for the same Notification

    For Notifications which send on Event Start and Event End, it would be useful to have the ability to have multiple Message Formats for the same Notification (one to send out at start, one to send out at end).

    Advantages:
    -Can include "End Time" in only the Notification sent at end (rather than showing an erroneous 1/1/1970 00:00:00 included in the Notification sent at start)
    -Can include "Duration" in only the Notification sent at end
    -Can fully customize different messages for start and end of the Event Frame

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow additional authentication types for web service delivery endpoints in PI Notifications

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

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow dots in JSON property names when using REST Delivery Endpoints

    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'].

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to modify SOAP xml format

    There are some cases when the sender wants to modify the format of the SOAP xml itself. Currently Notifications service constructs a XML request including all the variables provided by the wsdl.

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  7. PI Notifications - HTML editor for delivery formats

    In Design mode, I would like the ability to switch between to the HTML Code of the delivery formats in order to add richer content when I need to.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow Access to Analysis Variable Values in Notification Rules

    I tried to look but didn't see this requested. It would be very useful if the values of the variable(s) created in an Analysis could be accessed from the Manage Formats page of a Notification Rule. I know you can create output attribute and map the output of an Analysis to an attribute, then reference that from the Manage Formats page. However it would be much better if any variable created in the Analysis that is tied to the Notification Rule could be accessed when creating the email format. This would provide an easy way to for example create a…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  9. Different email formats for event start and end conditions

    There is a requirement to include different information in the email body depending on whether the notification is for the event start or end. Typically, the event start email includes the start time and start values and the event end email also includes the end time, duration, end values and aggregations. The same could be true for other delivery channels.

    Currently, the workaround is to create two Notification Rules, one for event start and one for event end, but this is not ideal.

    6 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  10. Global Resend and Non-Repetition Interval setting

    It would be nice to have the possibility of setting a global resend and non-repetition interval.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  11. Apply non-repetition interval for Notifications sent at Event End

    The Non-Repetition Interval in Notification Rules is currently only applied to Notifications sent at Event Start. I would like the Non-Repetition Interval to also be applied to Notifications sent at Event End.

    8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  12. Notifications new option to not be notified if child event frames are created

    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.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  13. Ability to clear and not send notifications on Notification service startup.

    We've had issue with Notifications spamming users with events should a PI collective member stop getting data.

    At times, we need to disable the notification service until we can resolve the issue. After the issue is resolved, we need to start the notification service, and need an option to have it not send past email notifications.

    To be clear, clear all past events on service startup.

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  14. Patch the persistent Test Send window outside of PI System Explorer

    From tech support case 00602329:

    In PI System Explorer, click on an element that has notification rules set up. Go to the Notification Rules tab, select a notification rule, click on Manage Formats, and click on Test Send. Enter an email address and click on Test Send. While the button still says "Testing", switch to another window. When the send is complete, the Test Send window will appear overtop of the window that you switched to. The only way to make it go away is to switch back to the PI System Explorer window.

    This situation came up when I…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  15. Change "EMail" to "Email" in the results of contact searches by email address

    Throughout PI System Explorer, the capitalized form of "email" is written as "Email" except in the results of contact searches by email address, where it is written as "EMail". Please change this to "Email" for consistency and correctness. See the attachment.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  16. Notifications Subscriptions Notify Option defaults to "Start and End"

    Many EFs are poor health in nature such that notifying the user when the event is ended is very important. Many users don't realize that this is an option. Either make start and end the default or present all choices more visibly to the user. This will reduce the amount of time users spend chasing poor health events.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable headers for SOAP web service end point

    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.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow Notification Display of the target attribute using any UOM

    We default Element Templates to SI Units as standard, which makes sense, but we have Sites that are Imperial and Sites that are metric. This extends to certain department (wells, for example) using different units of measure to the default.
    I need to be able to send notifications to some people in a unit of measure that is not the template default (i.e. imperial), but there is no ability to do this without making duplicate attributes with different default UOM's.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
  20. Send notification to additional persons based on change in severity

    A way to configure a notification rule to send to additional contacts when the severity status changes without creating a new analysis.

    Customer use case:
    Customer wants to scan devices. If a device fails to respond (I/O Timeout) over a short period of time, the event frame Severity is set to Warning and a notification is sent to IT. If the device remains offline for an extended period of time a child event frame is created and severity changes to major. When this occurs the customer would like additional people to be notified so they can go investigate the issue.

    5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA/PREVIEW
COMPLETED