Task Assignment

Hi Arjun,
I am trying this from my end, What I have observed if you give Deny access to Sub group 2,3 they will not able to see the task even they are part of Parent Group, because they do not have access(deny) to use that Process model .
If you will share the url with Sub group 2,3 they should get error "The Requested Task Is Not Available
The task may have been deleted or completed by another assignee.".
help me understanding the usecase little more, do you need Group 2 and 3 be able to see the task in the task list but not to open it?

Hi Sandeep,
We are working on 17.3, where it is allowing the members of Sub-Group 2 and 3 to accept the task when we share the url. I could replicate the same in 17.2 as well.
We need to display the task in readOnly format to Group 2 and 3 where they can see the task when provided with a URL (as task list would be embedded in another application) but should not be able to accept/act on it.

For read only data I would generally say newsfeed posts or dashboards would better serve this purpose. If you have to go this route, I think the best way to do this is to actually spawn two different tasks. One that is read only, and one that is not read only. You can assign the read only task to Sub Group 1 and Sub Group 2 and then the other task to Sub Group 3. The issue with this is that users in groups 1 and 2 will still have the option to accept the task, which won't let them do anything but will let them pull it out of the task list of other members of group 1 and 2 (group 3 will be unaffected since they actually have a different task). If this is not acceptable you could generate a task for each member of group 1 or 2, but if these groups are large this would be bad for performance so I wouldn't recommend it.

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.

I would agree with Sandeep , read only assignment is the right approach.

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.

Hi All,
Thanks for your help. We have raised an enhancement request with Appian to accommodate this functionality.