Task Assignment

Hi Arjun,

Have you considered making an rule input such as local!viewOnly in the interface for the task? You can check which sub-group the user is part of, and selectively enable or disable the editable fields in the interface. However, the user would still have to accept the task, they just would not be able to edit.

Alternatively, you could display the information from the task in a record or report. Instead of Sub-Groups 2 and 3 accessing the information through the task, they could view it elsewhere.

Hi Arjun,

Have you considered making an rule input such as local!viewOnly in the interface for the task? You can check which sub-group the user is part of, and selectively enable or disable the editable fields in the interface. However, the user would still have to accept the task, they just would not be able to edit.

Alternatively, you could display the information from the task in a record or report. Instead of Sub-Groups 2 and 3 accessing the information through the task, they could view it elsewhere.

Thanks for the suggestion amyw. If one of the users accepts this task (members from group 2 or 3), then the concerned group members (Group 1 members) would have to reassign that task to themselves whereas the use case specifies, it should be the same task, just that members of Group 2/3 should not be able to accept the task. Business does not want to display that data in a record or a report.

arjunm922 You could spawn two user input tasks - one for Group 1 and one for Group 2/3. In the user input task for Group 2/3 you make everything read only. When Group 1 completes a task you include logic to complete the appropriate task for Group 2/3.