They help defining the transaction's behavior.
Name: Subprocess name to be shown in the diagram.
Process: It allows selecting the process.
Subprocess Type: It allows selecting the process type. Sub-processes can be Chained or Nested. Values are:
Chained. The sub-processes modality assumes that a process instance causes the creation and execution of an instance of another process (the sub-process). Once the sub-process execution has started, the instance of the original process may finish or continue with its own execution, reducing interest in the sub-process created.
Nested. The nested sub-processes modality allows an instance of a process (child) to be completely encapsulated as a unique task within another process (parent). The parent process waits for the termination of the child process before continuing with its own execution. Therfore, there is a hierarchical relationship between the two processes. The hierarchical relationship may be extended through different levels, making up a group of nested sub-processes.
Visible in history: It indicates whether the task is to be shown in the history.
Roles: Associated roles to execute the task.
Subject Rule: It allows defining the subject of the task at runtime. It admits characters, attributes and relevant data (eg."Customer registration number"+CustomerId+&relevantData).
Advanced properties
Calendar: It allows determining the calendar with which the time will be counted through a dialog that shows all the calendars defined on the Knowledge Base (more info). If we don´t specify a calendar, the process will be continuous, 24 x 7. By default the calendar will be the process calendar if applicable.
Metadata: It allows setting metadata to the sub-process.
Adaptability
Selectable for ad-hoc: allows setting up whether the sub-process appears in the successor tasks selection dialog shown on completing an ad-hoc task.
Task Dimension
Dimension: allows setting up whether the activity is simple (“Escalate” value) or if it admits multiple workitems in parallel (“Vector” value).
Dimension Type: only visible when Dimension has the “vector” value, it allows setting up whether the number of workitems to be created is fixed (“Fixed” value) or dynamic (“Relevant Data” value).
Fixed number: only visible when Dimension type property has the "Fixed" value,. It allows specifying the number of workitems that have to be created.
Take Number from relevant data: only visible when the “Relevant Data” value is selected in Dimension Type property. It allows specifying the relevant data that will contain the number of workitems to be created. When the workflow engine creates multiple workitems of a task, it assigns an index to each. E.g.: if two parallel workitems are created, one of them will be assigned index value 1 and the other index value 2. This index is accessible through the WorkflowWorkitem data type Index property.
An example of the use of this property occurs when each workitem must receive a different value of a specific relevant data. In this case, you can have an array of relevant data and add a value to it for each parallel workitem to be created. Then, you can use the workitem index to obtain the value corresponding to this workitem from the relevant data array.
Event Handling
On assignment change: Change in the assignment of a task instance.
On deadline: Deadline of an instance (process or task instance)
On warning: Warning of an instance (process or task instance)
On new instance: A new instance was created (process or task instance)
On priority change: Change in the priority of an instance (Process or task instance)
On resource non available: There are no resources (users) available to process the task
On state change: Change in the status of an instance (process or task instance)