Infinity Process Platform helps you to model the scoped organization hierarchy and its departments. Based on the assigned scope, the workitems are visible to the participants. Perhaps before you take this tutorial, it is important to understand the concept of scoped organization structure, explicitly scoped and implicitly scoped organization structure. For more information, please refer to the chapter Scoped Participants in the Concepts part. Once you are familiar with key concepts, you can set to take this tutorial.
The use case example helps you to understand:
So, let's create an organization structure which departments have defined scope.
The ScopedOrganizationModel is modeled to explain four specific scenarios of the real world organization. The hierarchy in the organization has parent-child relationship that is maintained using the explicitly scoped and implicitly scoped department binding.
The parent-child relationship should be established among all the organizations.
The following screenshot displays the ScopedOrganizationModel which is used to explain the use case.
Figure: ScopedOrganizationModel Use Case Example
Once all the organizations are connected, define the scope for each organization.
To define the scope:
So note that at the apex, O1 organization is an un-scoped organization which is connected to explicitly scoped O21. Explicitly scoped organization O21 and O22 are at second level in the hierarchy. Explicitly scoped organization O31 and implicitly scoped O32 are at third level in the hierarchy. Explicitly scoped organization O41, implicitly scoped O42 and explicitly scoped O43 are at fourth level in the hierarchy.
Once the hierarchy and scope is defined for each organization, the following four scenarios get created:
These four scenarios are taken into consideration to show how hierarchy of any organization can fit into one of these scenarios.
Let's create a process to understand the third scenario that is explicitly scoped to implicitly scoped to explicitly scoped child organization O43. In this scenario, the workitem would traverse through organization O1 to explicitly scoped O21 to implicitly scoped O32 to explicitly scoped O43.
To start with:
Figure: Explicitly and Implicitly Scoped Process
The model should be created in a way that each workitem should traverse through the specified organization department. In this model, Role 1 has the right to trigger the first activity. So, the user who has rights of the Role 1, enters the nation data. The scope data Nation_Scope is created and connected to the activity called Role 1 to enter nation. Once the Role 1 specifies the nation, the activity should be in the bucket of explicitly scoped organization O21. Once O21 passes the activity, it should go to the implicitly scoped organization O32. Here the activity is connected with the scope data State_scope. Because the participant of the activity is O32, which is implicitly scoped activity, the correct process data should be entered. Else the activity would go to the default department. If the correct data is entered the activity goes to explicitly scoped organization O43.
Once the model is created, you need to define participants for each activity.
To define the participants:
Deploy the ScopedOrganizationModel.xpdl. For more information on model deployment, please refer to the chapter Deploying a Workflow Model from the Support Case tutorial. Once the model is deployed, you can view and create new departments and users in the Participant Manager view. For detailed information, refer to chapter Creating and Editing User Accounts of the End User Handbook.
If you want to omit the modeling phase and set up the scenario in minimum of time, you can import the model ScopedOrganizationModel.xpdl provided by Infinity Process Platform by extracting it from the scopedParticipants/dat folder residing in the following ZIP file: