In the Controls panel you should see the message: Test environment ready.

Click icon Open application  to access the test service.

The Applications start page is displayed. It lists all available processes in this service.

Hover over the name of your service to display the quick start icons.

Click icon to display the list of available start events for the process. You want to create a new instance, so click Start_Order_Approval_Process.

Role Test 1: Write and List Permission

Now 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.

Reminder

If you have finished tutorial 4, the new order limit is 500.

Create at least two different instances:

  • One instance should fit the order value limit.
  • One instance should exceed the order value limit.

Reminder

If you have finished tutorial 4, the new order limit is 500.

Now open both instances and check their behavior:

Current Task

Role Right of pas_tutorial_employee
for this Step

Instance Behavior
Show_approval_messageWrite
  • You are able to open the instance.
  • You can process the instance (you can click button OK in the form).
Check_orderList
  • You are not able to open the instance. The Processing...  message is displayed. It indicates:
    • that the instance is currently processed in task Check_order.
    • that you do not have the permission to execute this task.

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 did not have permission to perform the approval step. Therefore the instance that exceeds the order limit (created in test 1) is still available.

Create one new test instance that fits the order value limit.

Now open both instances and check their behavior:

Current Task

Role Right of
pas_tutorial_employee
for this Step

Instance Behavior
show_approval_messageWrite
  • You are able to open the instance.
  • You can process the instance (you can click button OK in the form).
Check_orderRead
  • You are able to open the instance.
  • You cannot process the instance: If you click any button in the form, you are transfered to the instance list and a toast message is displayed: You are not allowed to execute this operation (see screenshot).

Roles Test 3: Write Permissions for all Steps

Switch back to your process and change the role right of lane Supervisor to Write.

Save the change and open the application again.

Use icon to open the instance overview directly.

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 able to open the instance.
  • You can process the instance (you can click one of the two buttons in the form).

If you have confirmed or rejected, the form of the next process step is displayed.

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.
On this Page:

Related Documentation:

  • No labels