Posted: 29 Nov 2018 5:15 EST Last activity: 7 Feb 2020 16:32 EST
Notification framework: How to raise a new Notification
This framework is aimed to provide end-to-end infrastructure for applications to deal with notifications related capabilities on any channels and to help users stay informed about the important events in the application.
Notification rule: To capture Notification related data.
What to send?
Whom to send?
Where to send?
Web gadget (Pega 7.3) (Bell icon in Case manager portal)
Email (Pega 7.3)
Mobile push notifications (Pega 7.3.1)
Ability to define custom channels
Different ways to trigger a notification:
Smart shape in flows
Smart step in Case designer
Ability for end users to opt in or out for receiving notifications across channels
How to configure and send a new Notification:
Let's say we have a business requirement of sending out Notification to the sales team when a new Lead (case) is created.
Step 1: Create a new Notification rule in Lead class
Rule can be created from New --> Process --> Notification
Primarily there are three important details that need to be captured as part of a Notification rule form
Message: What is the message that needs to be conveyed
A field value to ensure localization
Can be parameterized to ensure content is rich enough to convey event information
Recipients: Who are the intended users that need to be informed about the event that occurred
Channels: How to convey the message to the intended users
Step 2: Raise this notification
Below options are provided to send the Notification
Send notification smart shape
pxNotify API activity
Send notification step in case designer
All these options take notification rule name as parameter
Where/what does this data transform do? I have a similar issue where I am to the point where notifications are getting created, and I can verify recipients from the database but they are not appearing on the recipient's portal in real time. The recipient has to refresh the screen or portal and only then the red notification number shows up on the bell icon. Is there any specific configuration needed to be have it appear in real time without a refresh needed?
In my setup right now the Notification is getting created correctly and the Recipients are also getting set correctly. I have verified those in the database tables and as well as by just simply clicking on the bell icon, that fetches the new notification.
The automatic refresh is still the issue that I am facing. Is there any configuration needed for that?
I am using Pega 7.4 right now. I did verify that the actual notification data is getting stored in the PC_work_notifcation but I was unaware of the second table you mentioned. I just went into verify and none of my records have entries there but I do see pulse and attachment notifications in this table. So I guess I am missing something on this end, what and where do I configure for this particular table?
I had been checking the PR_DATA_NOTIFICATION_RECIPIENT table and see entries being added in there but nothing in this Param table.
Hi John, sorry for the late response but below are a few additional details I've gathered.
1. Adding a notification via Pulse did not trigger the bell icon either.
2. Again trying this approach also did not trigger the bell icon.
I noticed you mentioned the agent pyProcessNotification in another post, I tried to search for this particular agent in my system and did not find it. I found a few when I searched for "Notification" and those are attached in screenshot, along with a few others for information.
I have also configured the same functionality of Notification Gadget using the "pxNotify" Activity, the notifications are coming properly but once th notification becomes READ, the count on the bell icon is not decreasing,The count gets updated only when the user logs off and login back . We are Using the OOTB Data page D_pyGetNotificationsCountForOperator, but as it is a page type D page, its not getting refreshed, can anyone please help me on this.