Managing notifications in Pega Predictive Diagnostic Cloud - Ability to configure applications in a system
As per the documentation in https://docs.pega.com/en-US/bundle/predictive-diagnostic-cloud/page/predictive-diagnostic-cloud/reference-guide/managing-notifications-in-pega-predictive-diagnostic-cloud.html , to configure notifications, only System can be selected and NOT individual applications in the concerned System.
A system could have multiple application being maintained by multiple squads and in this scenario, sending a daily digest for applications across the system to all application squad would not be a right choice to segregate responsibility in addressing the alerts/issues from the notification.
Is there a way to configure notifications in PDC on an individual application level rather than system level?
Accepted Solution
Updated: 16 Mar 2023 5:12 EDT
Pegasystems Inc.
GB
@SPKarthik our SME analysis of this requirement is as follows:
There is currently no way to do notifications at application level.
(a) Many of the events have no application context
(b) the logic for assessing notification frequency, threshold and duplication is driven by the event correlation (uniqueness); non-trivial to drive by both correlation and correlation/application.
Therefore this requirement cannot be seen as straight-forward to implement (which is why @RaghuramJ16633460 's suggestion of using reporting is sound).
PDC relies on application context data sent by the Platform. In many cases it is missing …. so on PDC side we will not be able to figure out which application is it from.
Right now if the application name is available, it is included in notification body.
I trust that this answers your question.
HCL
NL
@SPKarthik Probably create a report definition out of the notification in the system with application filter and schedule that to the intended DL might help.
Accepted Solution
Updated: 16 Mar 2023 5:12 EDT
Pegasystems Inc.
GB
@SPKarthik our SME analysis of this requirement is as follows:
There is currently no way to do notifications at application level.
(a) Many of the events have no application context
(b) the logic for assessing notification frequency, threshold and duplication is driven by the event correlation (uniqueness); non-trivial to drive by both correlation and correlation/application.
Therefore this requirement cannot be seen as straight-forward to implement (which is why @RaghuramJ16633460 's suggestion of using reporting is sound).
PDC relies on application context data sent by the Platform. In many cases it is missing …. so on PDC side we will not be able to figure out which application is it from.
Right now if the application name is available, it is included in notification body.
I trust that this answers your question.