Herramientas personales

SubProcess

De BPM, workflow, six sigma, business process, process management, business process management, BPMN, workflows, process automation, work flow, BPMS, Business Process Management Software, bpm software, workflow management, workflow software, ISO | BizAgi

Contents

Subprocess


Image:Modeling_the_Process7_Image001.jpgA Sub-process is a compound activity included in a process.  It is compound given that this shape includes, in turn, a set of activities and a logical sequence (process) that indicates that said activity can be analyzed at a finer level.


When the sub-process is collapsed, the details of the sub-process cannot be viewed.  The plus sign (+) indicates that the activity is a sub-process and it has a lower level of detail.


Image:Modeling_the_Process7_Image002.jpgWhen the sub-process is expanded, the details of the sub-process can be seen within the limits.

 

Example: In the loan request process, let’s suppose the disbursement activity does not consist only of the person in charge from the area of operations recording the final state of the disbursement and its information, but rather, all the related activities and the different parties involved must also be taken into account.  In this case, the disbursement activity would not be atomic and should be considered a sub-process.


Image:Modeling_the_Process7_Image003.jpg


Considerations


Image:Modeling_the_Process7_Bullet001.gif All processes modeled in BizAgi are potential sub-processes.

Image:Modeling_the_Process7_Bullet001.gif A sub-process can have Intermediate Events and Timer Intermediate Events associated with it

Properties


Image:Modeling_the_Process7_Bullet001.gif Global Properties (name, display name, description, help text, sub-process run time, cost, priority).

Image:Modeling_the_Process7_Bullet001.gif Events.

Image:Modeling_the_Process7_Bullet001.gif Alarms.


The following are other global properties that characterize sub-processes


Image:Modeling_the_Process7_Bullet001.gif Transactional

Image:Modeling_the_Process7_Bullet001.gif Embedded: Embedded sub-processes are those that share the same information or data as the parent process. The embedded sub-processes are not independent and usually correspond to a section or module of the same process; therefore, they must not be called sub-processes. The characteristics of data mapping (input and output) and the type of sub-process are not required when an embedded process is used. The embedded sub-processes can only be transactional. The embedded processes cannot be configured as multiple sub-processes.

 Image:Modeling_the_Process7_Image005.jpg

Note:  Embedded processes are not meant to be reusable.

Image:BizagiWiki_Bullet001.gif  Reusable: Reusable sub-processes are the sub-processes that have not been set as embedded. Unlike the embedded sub-processes, the reusable’s sub-processes do not share the parent’s data; the embedded sub-processes have their own data set, whose initial values can be inherited of the parent according to the input data mapping type or they cannot be updated at the parent level, according to the output mapping type, when leaving the sub-process. The sub-process type is applicable for reusable sub-processes; the sub-process type can be integrated or standalone. The reusable’s sub-processes cannot be transactional, and this type of sub-process can only be configured as a multiple sub-process.


Image:Modeling_the_Process7_Bullet001.gif Sub-process: This property corresponds to the process that will be instanced.

Image:Modeling_the_Process7_Bullet001.gif Sub-process Version: This corresponds to the version of the process that will be instanced.

Image:Modeling_the_Process7_Bullet001.gif Sub-process Type:

Integrated:  A sub-process is configured as Integrated when the total execution of the process is required before starting the following activity of the caller process. This behavior can be compared to the sequence pattern, where Activity B cannot be run until Activity A has ended.

In addition, if the parent process is cancelled or ends naturally via another option or path, such as canceling a process event, the sub-process will also be closed if it is not concluded.


StandAloneNon-integrated or standalone processes are processes that, although they are called on by another process, do not have to be run completely to go on to the next activity. In this case, the sequence pattern does not apply and the sub-process will not depend on the parent process; that is, if the parent process ends, the sub-process can remain in effect.

Example: if a claim associated to a credit process is enabled, it must be processed independently.  In this case, the process of complaints and claims will contain information from the parent process, but the credit process must carry on regardless of the status of the complaint or claim.  If the credit process is cancelled, the claim must still be processed.



Image:Modeling_the_Process7_Bullet001.gif Initial Mapping Type:  The initial data mapping type (or input) indicates the way in which the sub-process inherits the data of the caller process (parent process). Three types of initial mapping exist. Its recommended value is Automatic.

Automatic: Automatic: the sub-process inherits each of the values of the record corresponding to the parent process in the application entity.

Example: Initial mapping is automatic: If the process has an idRequest = 15 in the application entity, the sub-process will also inherit it.


Manual: User defined (address, origin, destination, task). Only the information from the application entity defined by the user will be associated with the new case in the application entity.  

 

Example: Initial mapping is manual:If the parent process has an idRequest = 15 and the idLegalProceeding = 9 and only the idRequest is required in the sub-process, it must be indicated manually.

 

None: None of the data from the application entity is mapped in the application entity for the cases that are opened.


Image:Modeling_the_Process7_Image006.jpg


Note: When you create a new instance of the sub-process, a new case is created and a new record is created in the application entity of the project. Initially, the parent process has different values for each of the attributes that form a part of the application entity (remember that in this entity, there should only be attributes related to the main entities of each process)


Image:Modeling_the_Process7_Bullet001.gif Final Mapping Type: The final mapping type (or output) defines the way in which the data of the sub-process are updated in the caller process (parent process). Three types of final mapping type exist. The recommended value for the final mapping type is none.


Automatic: Each one of the values of the registry corresponding to the sub-process is updated in the application entity of the caller process.

Example: Final Mapping is automatic:If the sub-process has an idRequest = 15 and an idAppraisal = 9, the parent process will inherit them.

 

Manual: User defined (direction, origin, destiny, activity). The information of the application entity of the sub-process will only be updated in the application entity of the caller process (parent process).

Example: Final Mapping is manual:If the sub-process has an idRequest = 15 and an idAppraisal = 9 and only the idAppraisal is updated, the parent will only inherit this value.


None: None of the data from the application entity is mapped in the application entity for the cases that are opened.

Note:The mapping types recommended are: automatic on entry and none on exit.  When selecting these two variables, be careful not to replace the value of an attribute that is already using the process.  For instance, if you select manual as the initial mapping type and automatic on exit, you may overwrite an existing value with an empty or null record.

 


Example sub-process

The Create Credit Cards sub-process is included in the loan request process.  In this case, just one sub-process is carried out for all the cards requested (for instance, the owner of the credit card and the additional cardholders).


Image:Modeling_the_Process7_Image020.jpg

 

Image:Modeling_the_Process7_Image021.jpg

 

In order to configure a sub-process, right click on the shape of the sub-process.  Click on Global Properties in the dropdown menu.

 

Image:Modeling_the_Process7_Image022.jpg

 

Configure the following global properties of the sub-process


Image:Modeling_the_Process7_Bullet001.gif Indicate whether the sub-process is transactional

Image:Modeling_the_Process7_Bullet001.gif Indicate whether the process is embedded or not.

Image:Modeling_the_Process7_Bullet001.gif The multiple sub-process is only selected when you want to create multiple instances of the sub-process (see multiple sub-process property).  In this example, only one is needed for all the cards, but if they are processed individually, the conditions would change and therefore, a multiple-sub-process would be necessary.

Image:Modeling_the_Process7_Bullet001.gif Select the sub-process that you would like to use from the list of existing sub-processes.

Image:Modeling_the_Process7_Bullet001.gif  Select the version of the sub-process.  In the event that there is only one version of the process, you do not have to select it.

Image:Modeling_the_Process7_Bullet001.gif Indicate the type of sub-process: The type of sub-process can be integrated, stand alone or none (the latter is the same as integrated).

Image:Modeling_the_Process7_Bullet001.gif Specify mapping type: initial and final (the latter only applies for integrated sub-processes).