Figure: Activity - General Properties
To view and modify the properties of an activity, select it in the swim lane. The properties window opens in the top right corner of the pane.
Figure: Activity - General Properties
To view and edit general properties of the activity, click the General Properties button.
Figure: Open General Properties
The General Properties section opens with the following entries:
icon on the right side
of the task type selection. This option is provided for all task types except manual tasks.
In case you switch to the Integrator profile, UUID and ID options are displayed additionally.
Figure: UUID and UI Properties
In case select the option Subprocess, the activity acts as a subprocess and the activity icon changes to the subprocess icon with a plus sign in the center-bottom of the activity. The adjacent drop-down list displays all the processes defined in all the models displayed under the My Process Models panel.
If you are working with the Integrator profile, an Execution option is available. This provides the facility to decide whether process can be executed synchronously or asynchronously. By default, the Synchronous/Shared Data option is selected. The drop-down list contains following options:
The Copy All Data option is disabled for the Synchronous/Shared Data option, by default.
Figure: Activity - Subprocess
For details on working with subprocess activities, please refer to chapter Configuring Subprocess Activities Configuring Subprocess Activities of the Modeling Guide. Modeling Guide in the Stardust Documentation.
The Processing Type drop list is enabled in case the subprocess is a Process Interface or an Application Activity type is specified...
The following processing types are available:
Figure: Processing Type
Selecting Multiple Instance parallel or Multi-instance sequential enables multi-instance processing for the activity and adds the appropriate symbol to the activity in the model diagram.
Note
Please use the sequential processing type with care. In some cases it might lead to uncompleted processes.
Figure: Activity symbol for parallel multiple instances
Figure: Activity symbol for sequential multiple instances
For details on the concept of using multi instances activities refer to chapter Using Multiple Instance Activities of the Concepts handbook. Using Multiple Instance Activities of the Concepts handbook.
For Multi-instance processing types you can navigate directly to the
Processing settings page by clicking the
icon on the right side
of the Processing Type selection.
Figure: Navigate to the Processing settings page
Click the 
icon to navigate to
the Processing type settings page.
Figure: Setting processing properties
The Processing Type selection field works as described in section Selecting the Processing Type.
In case Multi-instance Parallel or Multi-instance Sequential are selected, the following fields are enabled:
For details on supported parameter data types refer to section Supported Parameter Data Types of chapter Using Multiple Instance Activities of the Concepts Supported Parameter Data Types of chapter Using Multiple Instance Activities of the Concepts handbook.
The Input Parameter specifies the in data parameter definitions used for multi-instance processing. All IN data parameters defined for the application or process interface are available in the list, for example the parameter definition pointing to the list data element that you want to use to create activity instances from. The list element from the list data used for the multi-instance iteration will be mapped to this parameter. The parameter is required.
Select the parameter definition pointing to the list data that you want to use to create activity instances from.
Figure: Select Input Parameter
The specified input parameters appear as Input Access Point in Data Flow properties with (List) appended.
The Index Parameter is an optional parameter. It allows to map the access point into which the current list iteration index will be passed.
Figure: Select Index Parameter
The Output Parameter specifies the out data parameter definitions used for multi-instance processing. All OUT data parameters defined for the application or process interface are available in the list, for example the parameter definition pointing to the list data element used to capture data from each activity instance. This parameter is optional.
Select the parameter definition pointing to the data element used to capture data from each activity instance.
Figure: Select Output Parameter
The specified output parameters appear as Output Access Point in Data Flow properties with (List) appended.
In case of sequential processing, an additional option to limit the transaction batch size is provided. By default, the check box Limit Transaction Batch Size is disabled and all instances are processed in one transaction.
You can configure the number of instances to process in one transaction for sequential multiple instance activities by selecting this checkbox. Now the Maximum Batch Size entry field will be enabled containing the default value 1. Enter a batch size, which should be an integer value specifying the concrete limit. The transaction will be committed after processing of the specified number of instances. A new transaction or activity thread will be started for processing subsequent activity instances and the instance counter and transaction duration timer will be reset to 0.
Figure: Limiting the Batch Size
Note
Please use the limitation of the transaction batch size with care. In some cases the usage might
lead to uncompleted processes.
This option is available only when you switch to the Integrator profile. Using this option, you can select the application which is implementing the logic for the task.
Figure: Implementation
For the Manual task, auto-generated screen defines the underlying logic.
Figure: Implementation - Manual Task
In the implementation part for Rule tasks you can select a Rule set that has been created or imported in the Rules Manager. Click the drop-down list for the Rule Set field and choose one of the provided rule sets. Only one Rule Set can be selected per Rule Task.
Figure: Implementation - Rule Task
For details on creating or importing rule sets, refer to section Managing Business Rules in the Stardust Portal documentation.
During execution, the activity invokes the rules and decision tables pertaining to the rule set. Data Access Points for the Rule Tasks are computed from the selected Rule Set and exposed in the Data Flow. For details refer to section Setting Data Access Points for Rule Tasks of chapter Specifying Data Flows.
Rule Sets do not appear under the Applications node in the outline.
Note
You need a lifecycle management environment to be able to run and test a Rule Task.
Please contact our Sales Support Team for details.
For all the other tasks, excluding Manual, None and Rule tasks, you need to select the defined application from the Application drop-down list. It lists the applications from the current model and other models displayed under the My Process Models panel, according to the selected task.
Figure: Implementation - User Task
In case you like to view application properties on the selected application, click the blue arrow on the right side of the Application field. The appropriate application view opens with details.
Figure: Open the application properties view
Click the Display icon.
Figure: Display Icon
Select the Is Auxiliary Activity checkbox to mark activity as auxiliary from business perspective.
Figure: Is Auxiliary Activity
Click the Controlling Parameters icon.
Figure: Controlling Properties Icon
The following controlling parameters are available for activities:
Figure: Controlling
To add comments for activities, perform the following steps:
Figure: Activity - Comment Icon
Figure: Activity - Add Comment