Dynamic Organization Identifier Mapping

When a Dynamic Organization Participant is assigned to a task you need to identify the correct instance of the Dynamic Organization to use to resolve this participant at runtime. This is done using Dynamic Organization Identifiers which are mapped to process data.

Note: The mappings are between the process data and the Dynamic Organization Identifiers of the referenced Dynamic Organization (not the Dynamic Organization).

Procedure

  1. In the business process, select the Work Resource tab, and expand Dynamic Organization Identifer Mappings... .
  2. Map your process data (data fields and parameters) to a Dynamic Organization Identifier (which you set up when you created the Dynamic Organization Model). See "Dynamic Organizations" in TIBCO Business Studio Concepts and "Creating a Dynamic Organization" in TIBCO Business Studio Modeling User's Guide .

What to do next

A Dynamic Organization declares its Identifier Fields. These are arbitrary fields that are used to uniquely identify a generated instance of the Dynamic Organization at runtime.

When a Dynamic Organization is assigned to an Extension Point, those Identifier Fields must be mapped/assigned to named LDAP Attributes. This is done after deployment.

A generated instance of a Dynamic Organization takes its Identifier values from those named Attributes; of the LDAP Entry from which it originates.

A Dynamic Organization Participant carries values for the Dynamic Organization Identifiers. These values are derived from process data (data fields and parameters) mapped to those Dynamic Organization Identifiers. With this information the User Task can identify the instance of the Dynamic Organization in which the Participant can be found.