Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

About Notifications

About Notifications

A notification is a WS-HT construct that relies on a WSDL interface, people assignments, and other details that are incorporated into a People activity.
In BPMN, a notification is implemented within a Send Task or Message Send Event.
By itself a notification is not executable. It is designed to be used as an escalation action within a task or as the main construct of a People activity.
Unlike a task, a notification does not have an outcome. It relies on a one-way operation in a WSDL, serving to inform users of an event such as missed deadline or product ship date. Notifications usually are displayed in users’ task client application along with tasks. They could also be used in other forms, like email or text message, if you choose to create your own client applications.
The BPEL4People specification defines several ways that a People activity can incorporate a notification, as follows:
  • An inline notification declared within the People activity. The notification can be used only by that People activity. For details, see Creating an Inline Task or Notification.
  • A local notification declared within either the scope containing the People activity or the process scope. In this case, the notification can be reused as an implementation of multiple People activities enclosed within the scope containing the notification declaration. For details, see Adding a Task or Notification to the Outline View for Process or Scope Use.
  • An escalation action for a task deadline. For details, see About Task Deadlines and Escalations
  • (For future release.) A standalone notification identified using a QName. In this case the notification can be reused across multiple BPEL4People processes within the same environment.
A notification definition contains the following parts:
  • Notification Name, Priority, and Interface
  • Role Assignments for a Task or Notification
  • Adding Task or Notification Presentation Properties
  • Adding Rendering Details for a Task or Notification


Updated March 30, 2020