Configuring and Modeling the Processes
The process definition view consists of following three tabs:
In the Configure tab, you can define the properties of the process definition and associate business object with it.
Figure: Configure Tab
Viewing and Editing Process Definition Properties
You can specify following properties:
- Name - Specify unique name for the process. This is mandatory field.
- Business Object - This drop-down list contains a data scope or business entity. All current
Business Objects are listed, and each listed Business Object includes its model name. For example,
name of the model is OrderProcessing and name of the business object is Order. In this case, it would appear as
OrderProcessing/Order. Once the step is added in the Model tab, this field becomes disabled and
the user cannot change the Business Object. To leverage the applications, participants
and process interfaces created in the Modeling perspective, select the business object.
For details on Business Objects, please refer to the chapter
of the IPP
handbook in the Infinity Process Platform Documentation.
- Description - The Rich Text Editor is provided to specify header and description
for the checklist panel. You can use the rich text editor options like Bold, Italic, Strike Through etc. for the description.
You can also specify following tokens for the checklist panel header
which gets replaced with process data value at the time of execution.
So, following would be the token for the business object named Vendor which has
- $businessObject.<attributename> - Only top level attributes of a business object
are supported. For example, for the business object named Vendor, the
$businessObject.vendoraddress, $businessObject.ID, $businessObject.Name
Nested attributes are not supported.
If the address attribute contains nested level attribute called vendorcity then the
$businessObject.address.vendorcity is not supported. Note that multi-cardinality of
the attribute is also not supported.
- $businessDate - This token gets replaced with current date in the Checklist Panel header.
The checklist header gets displayed after model deployment.
- Manual Start Performer - The drop-down lists
all participants of all models from the model repository. Selected participant can start process
instances manually. The model does not become startable if the None option is selected.
You can use these simple models as templates which can be called as service tasks from other models of the
Model & Go! perspective.
For more information, please refer the section Service Task of the
chapter Using the Simple Process Definition Canvas.
In the Model tab, you can define the actual design of the process definition.
It contains the process definition canvas which consists of steps palette and series of rows that contains
process building objects.
Working with Process Definition Canvas
A process definition canvas contains steps palette and series of rows that contains
process building objects.
Process Definition Steps that is Process Topology are built by dragging steps from the palette
on the left and dropping them into a series of rows in the canvas. The stacking of the rows and the makeup
of each row (single cell vs. multiple) define the topology of the process definition,
whereby the process executes in the defined sequence from top to bottom.
Figure: Process Definition Canvas
For more information, please refer the chapter Using the Simple Process Definition Canvas.
You can deploy the model from this tab. Click Deploy to finish the deployment.
By default, the technical model
PredefinedModel gets deployed.
Deployment errors and warnings are displayed at the time of deployment in the dialog, if any.
Figure: Deployment Errors and Warnings