Conditional show of Accept, Re-assign buttons

It can be done ,Can we know where you got stuck  and the current design you have ?? In general we save Details related Assistant task. We use these details to validate against loggedinuser on manager task . If the current logged in user and the person who did the Assistant task are same .We will restrict him on opening/Completing manager task .

Thanks Venkat, you are right about the requirement.

I don't have any design yet. Is there any OOTB options to conditionally restrict while accepting/opening task and show error message?

You can easily use the OOTB assignment feature to do so. Just exclude the person completing the first task from assignment of the next one.

Depends on how you designing your process model , I mean these tasks going to be in Same Process model?? If Yes, remove chaining and exclude the person who did the task before in the assignment tab .If it's Database centric you can follow the steps i mentioned above .

2nd Task should go to Manager group, if I exclude the person(previous task performer) from Manager group, does that only impact that specific instance?

keerthik0010 said:

if I exclude the person(previous task performer) from Manager group, does that only impact that specific instance?

Yes, Save the tp!owner of Assistant task in process variable and exclude him in Manager task 

This should work fine if you can remove the user who has completed the 1st task (Save the tp!owner in a process variable from the 1st UIT output) from the list of users in the assignment of the task followed by the first one. below is a code you can reuse for that purpose.

a!localVariables(
  local!groupMembers: a!groupMembers(group: cons!YOUR_GROUP_CONSTANT).data,
  remove(
    local!groupMembers,
    wherecontains(
      tostring(pv!ownerOne),
      touniformstring(local!groupMembers)
    )
  )
)

This is a good example for using the set function difference().

difference(
  touser(a!groupMembers(<YOUR_GROUP>).data),
  <USER_SUBMITTED_THE_FIRST_TASK>
)

Thanks all for your response.

Excluded restriction is already there in the system. In fact same user can't be assigned to the next task.

Actual issue:

We have a Manager task list(customized) which shows all others tasks(assigned to other users and actual group tasks).

Since the user is part of the group he still can see the task via the customized list. This is implemented if any user who has assigned task and goes OOO, then other users can pick it up.

The requirement is to disable the accept, reject and re-assign buttons if the same user who has dual access (access to both the tasks) should be restricted to claim the Manager task/2nd task (if he already submitted Assistant/1st task) and show him an error/warning message.

Note: We shouldn't remove the task from the customized task list is the ask from business.

How is this "Manager Task List" implemented?

Background: Process models have the security role "Manager" which allows a person in that role to reassign any task to anyone.

So, there is no specific way to disable these buttons, but you can use the task assignment, task management and model security to set this up.