Step 3: Testing With Roles

In the Controls panel you should see the message Test environment ready. Click icon Open test application to access the test service:

The process table is displayed showing all processes available in your service. You can use the Play button here:

You can also click on a process to open its instance table. Here, you can also use the blue Play button to create a new process instance:

In role-based applications, role labels are displayed above the header of the instance table if your user is assigned more than one role. If your user has been assigned the roles that you created in step 1, you have two roles now:

• tutorial_employee

• tutorial_supervisor

Therefore, you should now see role labels for both roles:

Test Preparations

Create some test instances but do not finish them (see below):

If your order value is within the limit, do not click OK in the third form. Open the menu on top left and click the name of your process to go back to the instance overview:

If your order value exceeds the limit, you are currently not allowed to execute process step Check order. Click Back to Overview to display the instance overview:

Create at least two different instances:

• One instance should fit the order value limit.

• One instance should exceed the order value limit.

Result:

Role Test 1: Double Write Permission

Open both instances and check their behavior:

Role Test 2: Write and Read Permission

Switch back to your process and change the role right of lane Supervisor to Read. Save the change and open the application again:

Until now, your user could process all instances, no matter in which step they currently are.

For the next test, create again two different instances:

• One instance should fit the order value limit.

• One instance should exceed the order value limit.

Now open both instances and check their behavior:

Roles Test 3: Write and List Permission

Switch back to your process and change the role right of lane Supervisor to List. Save the change and open the application again:

Open the instance overview. Since your user did not have permission to perform the approval step so far, your test instance is still displayed in the instance list:

Open the remaining instance and check its behavior:

• You are not able to open the instance.

• You see the following screen:

Why is that?

Your user has two roles, both roles don’t have access to the instance.

• tutorial_employee: is not allowed for process step Check_order at all. In your process model, this step lies inside the supervisor’s lane.
  Go to the instance list and click role label tutorial_employee: His instance list is empty.

  

• tutorial_supervisor: has currently only list permission. Therefore, user’s with role supervisor can only see the instance list, but they are not able to open the instance neither to process it.
  Go to the instance list and click role label tutorial_supervisor: His instance list shows all instances that are currently in step Check_order.

  

Checking the Deployed Service

If you have followed all tutorials step by step, you can review the differences between a test service and a deployed service. So far, you have deployed the service only once in tutorial 4. The roles were implemented in tutorial 5. The deployed service should not yet reflect the implementation of the roles.

Open the deployed service:

Start the service to create a new instance:

You still see the order form created in tutorial 1 - without the label element created in tutorial 4:

And no matter what role permissions you store in the test service, you will always able to execute the Form_CheckOrder:

Congratulations - you have done it!
You have modeled your first role-based process and tested it.