The Modeling perspective visualizes the existing process definitions in the My Process Models panel under model element. You can create, rename and delete process definitions. Each process definition has its property panel wherein you can modify its properties. A typical process definition contains swim lanes, activities and gateways, applications, events, data and sequence flows.
You can perform following operations on any process definition in the Modeling perspective:
Perform the following steps to create a new process definition.
Figure:
Creating a Process Definition
Perform the following steps to rename the process definition:
Figure:
Renaming a Process Definition
Figure:
Specify New name
Rename can be performed in the My Process Models panel and the property panel of the element.
Under the My Process Models node, right-click the process name and select Clone.
The cloned process definition is displayed as CLONE-<processdefinitionname>.
Figure:
Clone Process
Under the My Process Models node, right-click the process name and select Delete. The process gets deleted.
Figure:
Delete Process
To edit properties of a process definition select the process definition under the My Process Models node in the outline tree. The properties window is displayed at the top right corner of the swim lane.
On the left side of the properties pane, you find icons to select the specific property type you like to view or edit.
Setting General Properties
Process Interface Properties
Display
Process AttachmentsIn the General Properties window of a process definition, you can specify the following properties:
The UUID and ID options are displayed only when you switch to Integrator profile.
| Priority Value | Priority Value Converts to |
|---|---|
| value > 0 (high priority) | 1 |
| value == 0 (normal priority) | 0 |
| value < 0 (low priority) | -1 |
Figure: General Properties of Process Definition
Optionally perform the following steps to specify a comment:
Figure:
Process Properties -Comments
To delete the comment, select the comment and click the Delete icon. The user, who has submitted the comment, only that user can delete the comment. If the other user selects the comment or no comment is selected, the Delete icon remains in disabled state.
Using the process interface option, the process definition of the provider model can be referenced in the consumer model. For more information about the process interface, please refer to the section Using Process Interfaces Using Process Interfaces of the chapter Creating Models With Cross References Creating Models With Cross References of the Concepts handbook in the Stardust Documentation.
To view and modify the process interface properties of a process, perform the following steps:

Figure:
Process Interface - Type
So there are three valid states concerning declared and implemented process interfaces:
This property defines the process interface. A model that wants to expose its process to other consumer model should choose this option. When a process interface property of a process definition is set to Provides Process Interface, it can be referenced from the consumer model. When you select the Provides Process Interface, the following options are displayed:
Figure:
Provides Process Interface

Figure: Add Parameters
Note
Primitive Enumeration types are not supported as formal parameters in case of
SOAP and REST external process invocation. Use a structured data type embedding
the required Enumeration type instead.
A model that wants to provide an alternate implementation of its process definition should opt for Implements Process Interface option. It provides an implementation for a process interface defined in a provider model file.
When you select the Implement Process Interface option, the processes available for implementation are listed.
Figure:
Process Properties - Implements Process Interface
When you select the process to be implemented, its exposed parameters are listed under process interface. Note that only Data parameter is editable. This Data field is populated only when you drag and drop the structured type from the Provider model in the Consumer model. Or when you create a data of the same Type and reference it in the Consumer model.
To edit or set data paths for a process definition, click the Data Path icon
on the left side of the properties panel. The
Data Paths panel opens with according properties. Please refer to chapter
Configuring Data Paths for details on these properties.

Figure: Process Properties - Data Path
Perform the following steps to modify the Display properties:

Figure:
Process - Display
In the Authorization property page, you can manage permissions for the process. You can assign or remove participants from specific process permissions.
Please refer to the chapter Setting Authorization in Model Element Properties for details on how to use the Authorization pane.

Figure: Authorization
Perform the following steps to specify if process attachments are supported:

For more information, please refer to the section Unique per root process instance Unique per root process instance of the chapter Working with Process Definition Working with Process Definition of the Modeling Guide. Modeling Guide in the Stardust Documentation.
Figure:
Process Attachments
Using this option, you can specify audit trail persistence modes. Perform the following steps to specify the runtime behavior.
Figure:
Runtime Behavior - Persistence
Though the default selection is Immediate; as long as you do not
change anything, the XPDL does not contain the attribute.
Note that you need to select and save the persistence
value explicitly to go into the XPDL.
For more information, please refer to the chapter Audit Trail Persistence Audit Trail Persistence of the Concepts Handbook Concepts Handbook in the Stardust Documentation.
The process can be referenced in another model only when the Provides Process Interface option is set for the process. The referenced process definition becomes the subprocess in the referencing model. Note that the elements referred externally are hidden in the My Process Models panel of the Consumer model.
Drag and drop the process from the referenced model.
Figure: Drag
Referenced Process Definition
If the selected subprocess is a referenced process from a provider model then the following execution types are available:
By default, Synchronous / Separate Data is selected. Note that in these cases invocation at runtime is always done via the process interface. If the selected subprocess is a process from the same model then the subprocess will be invoked directly at runtime as no process interface exists. For more information on execution types, please refer to the chapter Configuring Subprocess Activities Configuring Subprocess Activities of the Modeling Guide. Modeling Guide in the Stardust Documentation.
To define the dynamic binding, you need to have the referenced process added from the consumer model. Dynamic binding enables you to choose the implementation model at runtime. To enable the dynamic binding, you can mark the subprocess activity that invokes process interface, to be resolved at runtime.
Switch to Integrator profile. Open the properties of the referenced process definition and click on Implementation icon.
Figure:
Dynamic Binding
Specify the following details:
Qualified ID should be specified in the following format:
Qualified ID = {Model ID}Implementation Process ID. For example, {Model13}ImplementerProProcess1
For more information, please refer to the section Dynamic Binding Dynamic Binding of the Multiple Implementations Multiple Implementations chapter of the Multi Model Audit Trail Setups Multi Model Audit Trail Setups of the Concepts Concepts handbook in the Stardust Documentation.
A model using model elements from another model cannot be referenced by the other model. For example, if model B is referring elements of model A then model A cannot reference the elements of model B. Thus, circular references are not allowed between models. An error is displayed if you try to establish such a relationship between models.
Figure:
Circular Reference Error
For more information, please refer to the chapter Using Elements from Other Process Models Using Elements from Other Process Models of the Multi-model Audit Trail Setups . Multi-model Audit Trail Setups in the Stardust Documentation.
Processes that do not have process interface defined cannot be dragged and dropped across the models. If you try to drag and drop the process for which the process interface is not defined then the following message is displayed in the process diagram message area and the process does not get added to the process diagram canvas:
Figure: Drag
and Drop Process - No Process Interface
For more information, please refer to the section Dragging and Dropping of Elements of the chapter Swim Lanes Usage.
After creating a service wrapper process, you can create interface test process.
In the My Process Models panel, right-click on the created service wrapper process and select the Create Interface Test Process option.
Figure:
Create Interface Test Process
For more information on Create Interface Test Process option, please refer to the section Create Interface Test Process of the Specifying Applications chapter.