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

Logical People Group Parameters and Arguments

Logical People Group Parameters and Arguments

Add Logical People Group parameters.
A Logical People Group defined within the Human Interaction element can include parameters. They can be evaluated for specific people queries into an Identity service.
In addition, for each Logical People Group used in a task role assignment, you can add an argument expression for the parameter for that role assignment. When you associate the parameter with a search attribute in your LDAP or JDBC Identity service, the argument is resolved.
When you define a parameter, you can use it as follows:
  • In an assign activity, create an expression for a parameter when copying one Logical People Group to another. For example, you can write an XPath or XQuery expression that reflects the following logic: "The Logical People Group for the next task is the previous task owner's manager."
  • In a people query in the Process Deployment Descriptor, associate the parameter with a search attribute in your JDBC or LDAP Identity service. For example, associate the parameter
    country_code
    with an Identity search attribute called
    country_code
    .
  • In a role assignment within a task, create an expression for the parameter for a more specific people query in a JDBC or LDAP Identity service (not a file-based Identity service). As the parameter is resolved at runtime, the role assignment expression is also evaluated.
Example: Parameters in a Logical People Group Definition
<htd:logicalPeopleGroup name="regionalClerks">    <htd:documentation xml:lang="en-US">      The group of clerks responsible for the region specified.    </htd:documentation>    <htd:
parameter
name="
region
" type="xsd:string" /> </htd:logicalPeopleGroup>
Example: Arguments in Logical People Group Definition for a Potential Owner of a Task
<htd:potentialOwners>    <htd:from logicalPeopleGroup="regionalClerks">      <htd:
argument
name="
region
">        htd:getInput("part1")/region      </htd:argument>    </htd:from> </htd:potentialOwners>


Updated March 30, 2020