Creating a Scoped Organization Structure and a Scoped Model

Stardust helps you to model the scoped organization hierarchy and its departments. Based on the assigned scope, the workitems are visible to the participants. Before starting this tutorial, please make yourself familiar with the concept of scoped, explicitly scoped and implicitly scoped organization structures. For more information, please refer to chapter Scoped Participants in the Concepts part. Once you are familiar with the key concepts, you can start with this tutorial.

The use case example helps you to understand:

So, let's create an organization structure which departments have a defined scope.

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 Stardust by extracting it from the scopedParticipants/dat folder residing in the following ZIP file:

all-tutorials.zip.

Note that the provided example model contains other processes along with the one described below. These can be used to have a closer look on different scenarios.

Creating Scoped Organizational Structure

The example ScopedOrganizationModel is modeled to explain four specific scenarios of the real world organization. The hierarchy in the organization has a 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 organizational structure in the example model:


Figure: ScopedOrganizationModel Use Case Example

Defining the Scope of the Organizations

Once all organizations are connected, define the scope for each organization:

The hierarchy in the organizational structure is as follows:

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.

Creating an Activity Flow for Scoped Organization

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:

  1. Setup a dynamic Web project named multiscopexample. For detail instructions, please refer to the section Creating an Eclipse Project with Process Manager Facets from the Getting Started chapter of the Support Case tutorial.
  2. Once the multiscopexample project is created, we create a model named ScopedOrganizationModel.
  3. Create a process flow named Scoped Process:
    1. Create the first lane with participant Role 1, a manual trigger and activity Role1 to enter nation
    2. Create a second lane with participant O21 and activity Verify O21 is able to complete
    3. Create a third lane with participant O31 and activity To be completed by O32
    4. Create a fourth lane with participant O43 and activity O43_Verify activity goes to Nation_State


Figure: Explicitly and Implicitly Scoped Process

The model is created in a way that each workitem should traverse through the specified organization department. The workflow is as follows:

  1. Role 1 is authorized to trigger the first activity. Thus the user who is assigned to Role 1, enters the nation data.
  2. The scope data Nation_scope is created and connected to the activity called Role 1 to enter nation. Once Role 1 specifies the nation, the activity should be in the bucket of explicitly scoped organization O21.
  3. Once O21 passes the activity, it should go to the implicitly scoped organization O32. Here the activity is connected with the scoped data State_scope. Because the participant of the activity is O32, which is an implicitly scoped activity, the correct process data should be entered. Otherwise the activity would go to the default department.
  4. If the correct data is entered the activity goes to explicitly scoped organization O43.

Deploying the Model

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.