English
  • Informatica ActiveVOS Current Version
  • All Products

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

Back Next

Adding a Compensation Handler to a Scope

Adding a Compensation Handler to a Scope

A scope's activities can be compensated, or reversed when the scope is completed and when another activity causes compensation to begin.
To add a compensation handler to a scope:
  1. From the Process Editor canvas, select a scope.
  2. Drag a Compensation catch event into the scope or near the border of a collapsed scope, as the illustration shows.
  3. Drag activities into the compensation handler that will reverse the work of the scope's main activity. For a boundary event, you must link the handler to an activity to execute. The activity must be a downstream activity that has not yet executed.
  4. From another scope, create an activity that triggers the compensation handler for the completed scope.
The following illustration shows a parent scope, children scopes, and their compensation handlers.