Page History
...
In order to achieve this requirement, place an authorization algorithmon the task ReviewAndCloseCase (, as shown on the left) and specify below.
Specify a multivalued attribute in which all users are stored that may not execute this task (shown on the right).
...
, as shown below.
Now all that needs to be done is make sure that at the end of the ad-hoc tasks AddFiles, ContactCustomer, MakeAssessment and UpdatePersonalInformation, the attribute Control.CaseOwners is updated. See the images image below:.
...
The contents of the flows that are mapped to the ad-hoc tasks AddFiles, ContactCustomer, MakeAssessment and UpdatePersonalInformation is out of scope, but make sure that at the end of the flow, the user who has performed the task (by default stored in system.user.id) is added to the multivalued attribute Control.CaseOwners. This is achieved by updating the value of the attribute Control.CaseOwners with its old value (Control.CaseOwners), combined with system.user.id.
When a user, who has previously performed either of the ad-hoc tasks AddFiles, ContactCustomer, MakeAssessment or UpdatePersonalInformation, tries to perform the task ReviewAndCloseCaseat runtime, the following message will appear:
...
Overview
Content Tools