Can dynamic endpoints send AF Notifications to contact groups?

Hello. You don't need to modify anything in the endpoint, have a look at this video from 06:10 to see how you add individual users or groups to the notification subscription list: https://youtu.be/JGwCtMSos9w?si=grB8M6RD3V_wAzpq

Hello. You don't need to modify anything in the endpoint, have a look at this video from 06:10 to see how you add individual users or groups to the notification subscription list: https://youtu.be/JGwCtMSos9w?si=grB8M6RD3V_wAzpq

Unfortunately this does not solve my problem. I have several elements created from a common element template, but each element's notification rule needs to send the notification to a different group of people. If I configure student1@email.com as the subscriber on the template, each site's notification will be sent to that same email address. I need each notification to be sent to a different subscriber list for each site.

Right, so I read your question again and will try to answer more detailed.

I thought you were talkign about the configuration of the actual email delivery channel but now I see it's the dynamic endpoint you're talking about. I don't think this allows you to specify multiple emails in one go.

An alternative we've used several times is to create email distribution groups in your company email server instead, so you get group1@yourcompany.com as a single email to use in PI Notifications. The email system is then responsible for distributing the email to anyone in that group. An advantage to this solution is managability, you basically configure this once in PI System Explorer and then your IT dept. manages who belongs to each group. A disadvantage to this solution is that you're not able to utilize the Escalation teams feature.

If you want to continue using contact groups defined in AF, I would recommend looking into adding more triggers to your notification rule, so you have one subscription per trigger. I would then add some criteria to the trigger to determine if the emails should go to group1, group2, etc.

After instantiating your AF Elements from the template you would need to configure some things manually for each element, to indicate where the notifications should go. So if you add some meta data manually or perhaps configure a StringBuilder attribute to provide it automatically, you could include this as part of the notification rule trigger. Then you subscribe the correct contact group to this notification rule trigger, and repeat for any group needing to be notified.

This is a bit more work than the previous solution, but you don't need to include your IT dept and you have full control inside AF. Escalation teams also works, meaning that if the first person doesn't acknowledge the notification in due time, the notification will be escalated to the next one on the list.

Thank you. I figured that some workaround like this would be necessary.

Hi,

I do need the solution of this particular case (which you posted above).

It would be very helpful for me, if you have got some solution, please share the same here.