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

Sending Email When a Task Deadline Occurs

Sending Email When a Task Deadline Occurs

The Send Email action is an extension escalation provided by Informatica. When a deadline is reached, an email can alert a task owner or administrator about a late task. For a discussion of escalations, see About Task Deadlines and Escalations.
Sending email requires that you set up the Email Service in Process Server. The Email service provides a default sender's email address, which you can configure. For details, see the
Process Server Online Help
.
To Create a Send Email Action:s
  1. In the Outline view, right mouse click on
    Task > Start (or Completion) Deadline > Send Email
    .
  2. In the Email tab, add an expression for one or more recipients. The assignment you make to recipients must evaluate to the
    hd:organizationalEntity
    data type, defined in the WS-HT specification. Typing the name of a Logical People Group or a user name is not a valid value. To create a valid expression, use a Human Task custom function from the Expression Builder, such as:
    htd:getPotentialOwners("reviewTask")
  3. Add an expression for the Subject and for the Body of the email. To write these expressions, see the example below. Also, see Email Service in the
    Process Developer Online Help
    for some tips on creating the Subject and Body using expressions.
  4. Optionally, add a condition, as described in Defining a Condition for an Escalation Action.
Here are examples of valid email values:
  • Recipients:
    htd:getLogicalPeopleGroup('loanreps')
  • Subject:
    'New task in Central'
  • Body:
    concat('Please review new loan for ', htd:getInput('Document')/loan:lastName, 'which has just arrived in Process Central.')

0 COMMENTS

We’d like to hear from you!