Activities can be started in assembly line mode in the activity execution view of the Workflow Execution Perspective, if they have the according configuration as described in the following sections.
Participants can be configured for assembly line mode in their property page by
setting the task assignment mode to Assign Automatically.
For information on how to set this property, please refer to section
Task Assignment of chapter
Modeling the Organizational Structure in the
Stardust Documentation - Eclipse Modeling Guide
Task Assignment of chapter
Modeling the Organizational Structure in the
Eclipse Modeling Guide
and to section
Viewing Role Properties
of chapter
Modeling the Organizational Structure
in the
Business Process Modeling Handbook
respectively.
You can determine if the assembly line mode is supported by adding the property
Carnot.BpmClient.Features.AssemblyLineTaskAssignment to your
carnot.properties file, residing in the ipp-resources folder
of your Web application. If set to false, the assembly line mode is
not supported and no assembly line entries are displayed in
the My Assignments section.
Carnot.BpmClient.Features.AssemblyLineTaskAssignment = false
Setting the property to true, which is the default value, the
assembly line mode will be supported again.
The logic to decide which assembly line has to be activated next is
implemented via an assembly line activity provider class, which has to
implement the interface IAssemblyLineActivityProvider.
The property Carnot.ProcessPortal.AssemblyLineActivityProvider
determines the provider class to use. Per default, this is set to:
Carnot.ProcessPortal.AssemblyLineActivityProvider =
org.eclipse.stardust.ui.web.processportal.common.DefaultAssemblyLineActivityProvider
In case you created a custom implementation class, change the value accordingly. Please refer to chapter Implementing an Assembly Line Activity Provider of the section Implementing Interfaces for Portal Configurations in the Stardust Documentation - Modeling Guide Implementing an Assembly Line Activity Provider of the section Implementing Interfaces for Portal Configurations in the Modeling Guide for detailed information on the interface.
In case activity criticality is set, the assembly line provider reduces the top element from an activity list for the relevant participant.
To implement the activity criticality, the assembly line provider should point to the class
org.eclipse.stardust.ui.web.processportal.common.CriticalityAwareAssemblyLineActivityProvider
instead of DefaultAssemblyLineActivityProvider class.
For details on activity criticality, refer to chapter Activity Criticality of the Stardust Concepts section. Activity Criticality of the Stardust Concepts section.
With the property Carnot.BpmClient.Features.AssemblyLinePushService, you can determine the behavior of the complete and suspend / suspend & save actions.
In case the value of this property is false, which is the default value, the actions to complete, suspend / suspend & save behave as follows:
In case the value of this property is true, the behavior of the complete, suspend and suspend & save actions depends on the enabled or disabled assembly mode in the following way:
Assembly line mode enabled:
Assembly line mode disabled:
If running in assembly line mode and the property Carnot.BpmClient.Features.AssemblyLinePushService
is set to true in your carnot.properties file, the Assembly Line
icon is available in the toolbar of the activity execution view.
Clicking this icon enables or disables the assembly line mode:
/
.

To switch to disabled, click the
icon.

To switch to enabled, click the
icon.
In case the assembly line mode is switched to enabled, the workflow portal returns to the normal work assignment mode, when the currently activated Activity is completed, suspended, or delegated.