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

Defining a Condition for an Escalation Action

Defining a Condition for an Escalation Action

As you define deadlines for the start and completion of a task, you can add a condition for triggering an escalation action. For example, you can check to see what the current priority of the task is, and if it is a high priority, trigger the escalation action. Escalation actions include notifications, reassignments, and process invocations, as described in Selecting an Escalation Action to Occur When a Task Deadline is Triggered.
If you add a condition to an escalation action, the escalation does not occur unless the condition evaluates to true.
Adding a Condition for an Escalation:
  1. Open the Properties view of an escalation, such as an inline notification under a Start Deadline of a task.
  2. Select the Dialog (
    ...
    ) Button at the end of the Condition text box.
  3. In the
    Condition Builder
    , select the functions and variables for your condition. For example:
    htd:getInput("ClaimApprovalRequest")/amount < 10000
In this example, the
amount
part of the
ClaimApprovalRequest
variable must be less than $10,000 in order for the condition to evaluate to true.
As you write conditions, you can take advantage of the Human Task functions, in particular the
getInput
function shown in the example. This function returns data from a running task instance.


Updated March 30, 2020