Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Notifying participants about events

Updated on May 11, 2022

Escalate expired service-level agreements and highlight cases that require immediate action by sending email and push notifications to case participants. You can use push notifications for mobile devices, and set up email notifications for all devices that support email. As a result, you ensure that business processes reach resolution within the defined time frame.

For example, a case worker can receive an email and a push notification after a goal for an assignment expires, or after an application routes a new assignment to the user.
All assignments in a case life cycle inherit the notification policy from the case type. The following scenarios do not support notifications:
  • You set the notification policy after creating an assignment.
  • A user pulls an assignment from a work queue.

    Users can receive notifications after an application routes an assignment to their worklists, but not after pulling assignments from shared work queues.

  • A user transfers ownership of an assignment to another user.
  • An application routes the assignment to the worklist of the user who already processes the case.

When your application sends an email, the system updates the pxSendDateTime property on the pxCorrSummary work page that belongs to pyWorkPage. Such updates might cause issues with refreshing a case at run time. To prevent errors, the pyEnableCorrSummary when rule is set to false by default, and the system does not update the pxSendDateTime property. If your business scenario requires updating the pxSendDateTime property, in Dev Studio set the pyEnableCorrSummary when rule to true.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us