English
  • Informatica ActiveVOS Current Version
  • All Products

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

Back Next

About Logical People Groups

About Logical People Groups

Add Logical People Group parameters.
A
Logical People Group
 is a named list that represents users or groups defined in an Identity Service, such as your company's LDAP directory. The Identity Service must be configured and enabled in the Process Console. Instead of naming the actual users or groups who can manage processes and tasks, you can refer indirectly to them from a Logical People Group.
The Logical People Group, such as
customer service representatives
, can have a parameter, such as
regions
, that can be associated with an expression, such as
region one
. Parameters can be used in an assign activity or with a people query at deployment time (for a JDBC or LDAP Identity service). At run-time, the parameters get resolved.
You can use Logical People Groups in defining task and notification assignments.
For example, you can define a Reviewers Logical People Group as a global construct and then use that Logical People Group within one or more tasks requiring reviewers. The users or groups are actually selected at deployment.
Logical People Groups are global elements enclosed in a Human Interactions extension element. The XML syntax for a Logical People Group element is: 
<htd:logicalPeopleGroups>?
   <htd:logicalPeopleGroup name="NCName" reference="QName"?>+
      <htd:parameter name="NCName" type="QName" />*
   </htd:logicalPeopleGroup>
</htd:logicalPeopleGroups>
The
parameter
 element is used to pass data needed for a dynamic assignment of a Logical People Group in an assign activity or for a role assignment within a task. A parameter can also be resolved with a people query evaluation at deployment for JDBC and LDAP Identity services, but not file-based services, such as tomcat-users.xml.
You can define several parameters of which some, none, or all of them can be evaluated and used in assignments or in the PDD. In addition, the parameters can be overridden in the Process Deployment Descriptor file.
Logical People Groups can be defined either at the process level or on enclosed scopes.