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

Designer

Designer

About Task Deadlines and Escalations

About Task Deadlines and Escalations

Select a deadline event (escalation) to view its definition.
You can specify one or more deadlines by which a task must be started and also one or more deadlines by which a task must be completed. If a start date or completion date is missed, you can trigger one or more escalation actions. For example, set a "start the task" deadline for three hours after a task is created, and if the deadline is missed, send a notification to the task's owner. If the second deadline is missed, alert the business administrator.
In addition to the simple example of notifying a task owner when a task is late, there are many expressions and conditions you can apply to a task deadline.
Note the following about setting deadlines:
  • Start deadlines describe when a potential owner must start working on a task. The deadlines are enabled as soon as the task is created and are disabled after a potential owner starts the task.
  • Completion deadlines describe when an owner must complete a task. The deadlines are enabled as soon as the task is created and are disabled after an owner completes the task.
If a task is reassigned, which changes the task state to unclaimed, the original deadlines are still in effect. For details,
see About Task LifeCycle
.
See the following topics for details on setting deadline alarms and escalation actions.
  • Adding Start and Completion Deadlines and Alarms
  • Selecting an Escalation Action to Occur When a Task Deadline is Triggered
  • Defining a Condition for an Escalation Action
  • Using Task Data or Mapped Data for a Notification
  • Creating an Inline or Local Notification Action for a Task Deadline
  • Using a Reassignment Action for a Task Deadline
  • Invoking a Process When a Task Deadline Occurs

0 COMMENTS

We’d like to hear from you!