Swim lanes are assigned to participants - roles or organizations. Users assigned to these roles or organizations perform the work represented by an activity instance. Being assigned one or more swim lanes, a user can perform the activities associated with those swim lanes by completing the work items in his worklist.
Hence, there is a distinction between
Consequently, in your modeling environment you use roles and organizations. Individual human performers are created and assigned to these roles in the Stardust Portal or console administration tools or via embedding application. The following sections describe the usage of participants in Modeling perspective:
You can work with following elements in the Participants node:
The elements are represented in the model tree as follows:
Each model has at least one role created by default, which is the Administrator role.
An organization element represents a group of resources. For example, a department or any organizational unit. This section describes how to work with organization elements and its properties.
To create an organization, right-click Participants node in the My Process Models panel and click Create Organization.

Figure: Create Organization
To rename the organization, right-click the Organization node in the My Process Models panel and click Rename. Specify the new name for organization.

Figure: Rename Organization
Rename can be performed in the My Process Models panel and the property panel of the element.
To delete organization, right-click the Organization node in the My Process Models panel and click Delete.

Figure: Delete Organization
To create a role under organization, right-click the Organization node in the My Process Models panel and click Create Role.

Figure: Organization - Create Role
The role created under organization can be set as manager. Right-click on the role created under organization node and click Set as Manager.

Figure: Role - Set as Manager
The role set as manager is indicated in the organization hierarchy with a red color role icon.
![]()
Figure: Role set as manager
Note that at a time you can set only one role under organization as a manager. If the role is already set as a manager or the role is not in the hierarchy of an organization, the Set as Manager option is grayed out.
To create an organization under organization, right-click the Organization node in the My Process Models panel and click Create Organization.

Figure: Organization - Create Organization
To view organization properties, click the Organization node in the My Process Models panel. The organization properties get displayed.

Figure: Organization Properties
Following properties are displayed:
The UUID and ID options are displayed only when you switch to Integrator profile.


Choose Assignment) or by automatic assignment (Assign Automatically) for using the
assembly line mode. Please refer to chapter
Working in Assembly Line Mode in the
End User Handbook
for details on using the automatic assignment for assembly line mode.



You can create roles using two ways:
To create a role, right-click the Participants node and click Create Role.

Figure: Create Role
To rename the role, right-click on role and click Rename Role.

Figure: Rename Role
Rename can be performed in the My Process Models panel and the property panel of the element.
To delete the role, right-click on role and click Delete Role.

Figure: Delete Role
To view role properties, click on role of which you want to view the properties.

Figure: Role Properties
The UUID and ID options are displayed only when you switch to Integrator profile.
Choose Assignment) or by automatic assignment (Assign Automatically) for using the
assembly line mode. Please refer to chapter
Working in Assembly Line Mode in the
End User Handbook
for details on using the automatic assignment for assembly line mode.
Figure: Role - Controlling
Figure: Structured Type - Comments
A conditional performer is evaluated at runtime and determines the identity of the actual performer. A conditional performer can be created only at the root node, that is, Participant node. You can neither create it nor drag and drop it under the Organization node.
The following sections help you to work with conditional performers.
To create conditional performer, right-click Participants node and click Create Conditional Performer.

Figure: Create Conditional Performer
To create conditional performer, right-click on conditional performer in the Participants node and click Rename.

Figure: Rename Conditional Performer
Rename can be performed in the My Process Models panel and the property panel of the element.
To delete conditional performer, right-click on conditional performer in Participants node and click Delete.

Figure: Delete Conditional Performer
To view and edit the properties of conditional performer, perform the following steps:

Figure: Properties of Conditional Performer
The UUID and ID options are displayed only when you switch to Integrator profile.


If you select User as a performer type, then you can specify data for the user realm. For more information, please refer to the section User Realm User Realm of the chapter Managing Multi Partition Stardust Installations Managing Multi Partition Stardust Installations in the Stardust Documentation.

Figure: User Realm

Figure: Conditional Performer - Comments
The conditional performer cannot be set as a participant for Manual or Scan events. A validation message is displayed in following scenarios:

Figure: Conditional Performer - Validation Message

Figure: Conditional Performer - Validation Message
You can reference participants from other models. For example to define a participant from another deployed model as performer of a lane, perform the following steps:

Figure: Swim Lane - Participants - Provider Model

Figure: Participant Referenced for Swim Lane
Note
If a participant with an identical ID already exists in the consumer or referencing model you cannot refer the
participant of the referenced model.
Even if you select the role with the identical ID of the referenced model, the participant with the same ID of the
current model is used. For example, if a role Role 1 exists in a referenced model
Provider and you also have a role with ID Role 1 in the consumer model, the role of
the consumer model gets assigned even if you select the role Provider/Role 1 from the referenced
model.