Defect #1527
closed
Task #1503: Testing of the product (9.4.0)
One incompatible role missing on saving the request
0%
Description
Role request: creating a request (for oneself) - incompatible roles
TC 92: https://kiwi.czechidm.com/case/92/
Scenario: An employee creates a request for 2 incompatible roles + another role (3, in total)
Given the user has a valid contract
And with the following authorizations:
userRole
When they file a new request for 3 roles with different criticality, 2 of which are incompatible, and submit it
Then the request is saved, split into 3 subprocesses, and displayed accordingly
And moves down the process line accordingly to be approved.
role 1 (ROLE_zaklad) - criticality 2
role 2 (subAdmin) - criticality 3 (incompatible)
role 3 (configAdmin) - criticality 4 (incompatible)
When I save my request, the form drops one of the incompatible roles, and saves just 2 subprocesses.
Files
Updated by Vít Švanda about 5 years ago
- Status changed from New to In Progress
- Assignee changed from Vít Švanda to milus kotisova
I think, the problem is in criticality 4 what you have set. This criticality is not defined by default, it means criticality 4 is same as 0 (criticalites/priorities are described in the wiki). This is reason why was subprocess automatically approved. For better view try to see audit of WF process for this subprocess.
Behavior is correct by me - concept of role is not missing, but was only approved.
Updated by milus kotisova about 5 years ago
- Status changed from In Progress to Closed
I confirm it works fine. Closing the ticket.
Updated by Radek Tomiška about 5 years ago
- Status changed from Closed to Rejected