The Role Concept of the Instance List
The Designer provides you with a role-based authorization concept (similar to the role-based authorization concept to run applications) that allows you to define which user is authorized to see the instance list of the respective process.
Each process has its own instance list. To access the role editor, select the respective BPMN model of your service on the diagram pane and switch to the attributes panel. Click Open role editor next to attribute Roles:
The role editor opens. The dialog initially contains an empty line to enter a role. The handling of the role editor is described in detail on Modeling Roles. There is one difference to the role editor of the instance list: Here, you have no radio buttons to assign different rights to roles:
If no roles are assigned, the instance list is available for all users and a corresponding note is displayed.
The Role Concept in the Executed Application
Our example illustrates the usage of roles in the instance list. In the example, users David Stringer and Jane Marple have the following roles assigned:
Name | Role |
|---|---|
David Stringer | ACME Employee |
Jane Marple | ACME Manager |
The following roles have the permission to see the instance list:
ACME CEO (acme_ceo)
ACME Manager (acme_manager)
Jane Marple has the role ACME Manager and thus has the necessary rights to see the instance list. In the application, she will see the option for adding a new instance as well as for opening the instance list (see Creating a Process Instance) when hovering over the service name:
She can use the magnifier to open the instance list. All running instances are displayed:
David Stringer has the role ACME Employee and thus has not the necessary rights to see the instance list. In the application, he will only see option Plus to create a new process instance. For him, the option to open the instance list is not displayed and so he cannot access the list:
