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

Adding Scheduled Actions for Tasks

Adding Scheduled Actions for Tasks

You can schedule activation and expiration times for tasks. These properties do not apply to notifications.
  • Deferred Activation for a Task
    You can specify an alarm for when a task should become active. The alarm is defined as either the period of time after which the task reaches the Ready state (in case of explicit claim) or Reserved state (in case of implicit claim), or the point in time when the task reaches Ready or Reserved.
    For example, you can specify, "Activation of this task is deferred until the time specified in its input data."
  • Task Expiration
    You can add a task expiration duration or date, if desired. The expiration indicates the date/time a task becomes obsolete, and the expiration date/time is displayed in users’ task client application. When the expiration occurs, all task instances are listed as exited, and a fault is thrown in the BPEL process. A user cannot complete the task, and the output data, if sent back by a user, will not be used.
For example, you can specify, "This task expires when not completed within 14 days after having been activated".
To Specify a Deferred Activation:
  1. Select the Properties view of a people activity.
  2. Put the All tab in focus.
  3. In the Defer Activation Alarm row, select Deadline or Duration.
  4. In the Defer Activation Expression row, select the Dialog (
    ...
    ) button to open the Expression Builder.
  5. Create either a deadline or duration expression. For examples, see "Deadline and Duration Expressions" in the
    Process Developer Designer Online Help
    .
Repeat the steps above to create an Expiration Alarm and Expiration Expression.


Updated March 30, 2020