Follow Our Example User Story

David Stringer wants to add roles to his order process. To do this, he needs to insert lanes into the BPMN model and assign the appropriate roles.

Good to Know

In role-based applications such as approval processes, roles are assigned to individual users. Each of these roles is associated with special rights. These decide which actions the respective user can perform, which data he or she can display and edit.

Roles are managed and assigned in the user management. Users of the Scheer PAS Designer are able to create them in the role editor. But only users authorized for user management can assign roles to specific users. Refer to Assigning Roles in the Designer guide for details.

For more information about role management in the Scheer PAS User Management, refer to Managing Roles in the Administration guide.

Add Lanes for the User Roles

In tutorial 1, you have created BPMN model Order_approval_1.
Open the BPMN model. It forms the basis for the following steps.

Select a lane element from the elements toolbar on the right side of the BPMN editor and drag it below your BPMN diagram.

If you click on the lane element at the lower right edge, you can enlarge the element.

Enlarge it to the point where the entire BPMN process could fit inside.

You need a separate lane for each role you want to use in the process. All role lanes must be modeled within one main lane. You have created the main lane, now drag two more lanes into it.

Click on the image to run through the animated version once. Click again to repeat.

Lane handling can be tricky. If you have problems placing the lanes correctly, we recommend to have a look at the explanations on our documentation page Lane > Notes on Lane Handling


Arrange the two new lanes within the main lane.

If you want to adapt a lane element, select it by clicking on its name or border.

The selected lane is outlined in bold and a black square will appear at the lower right edge. Use the square to adjust the size of the element.

Click on the image to run through the animated version once. Click again to repeat.

Configure the Lanes

Follow Our Example User Story

David has added the lanes. Now, he can configure the lanes and name them according to the roles he wants to use them for.

Select the lanes one by one and assign the following names in the Name field of the Attributes panel:

  • Main Lane: Administrator
  • Lane 1: Employee
  • Lane 2: Supervisor

In the next step, you are going to assign roles to the lane elements.

The administrator should be able to execute the whole process, so you will not assign any role to lane Administrator .

Select the Employee lane. Go to its attributes panel and click icon to open the Role Editor.

In the role editor, you can search for already created roles to reuse them or create your own roles.

You can also define different rights to each role:

RightDescription
WriteA user assigned to this role will be able to see and change the instance data for all process steps in the current lane.
Read

A user assigned to this role will be able to display the instance data for all process steps in the current lane.

This right is assigned by default.

ListA user assigned to this role will only be able to see the instances in the instance table for all process steps in the current lane.


The roles needed for this tutorial have already been created in the user management:

  • pas_tutorial_employee
  • pas_tutorial_supervisor

In a real process, you would assign the employee role to lane Employee and the supervisor role to lane Supervisor. However, since you are working on a tutorial, you should be able to execute the entire process with your personal user. Your user is assigned only the pas_tutorial_employee role.


So that you can recognize the different role rights, please configure your lanes as follows:

LaneRoleRight
Administrator nonenone
Employee

pas_tutorial_employee

Write
Supervisor

pas_tutorial_employee

List

In the next step, you will remodel your process.

Step 2: Remodeling the Process

On this Page:

Related Documentation:
  • No labels