Solved

Conditional show of Accept, Re-assign buttons

Forum|Forum|1 year ago
January 28, 2025
14 replies
0 views

Hi,

If a user is part of 2 groups: Assistant and Manager.

Same user who submitted a task as an Assistant shouldn't be able to access next task in the flow as Manager.

Is there a way not to show/disable the accept and reassign buttons when the same user tries to claim the task?

Or can we show an error message when trying to accept?

Any help/ideas are appreciated.

Thanks,
Keerthi

Best answer by mikes0011

Pass the username of the previous user into the Manager Review task. You won't be able to disable the "accept" button, but you can do on-form checks to check whether the task's viewer is the same as the previous user, and display a validation message alerting them that they are not allowed to perform that review.

Then they could either use the OOB "reject" button or, as a special case, you could build a custom Submit Button saying something like "send back to reviewer group", which would simply exit the task and loop immediately back to it allowing the original group assignment to take hold again regardless of the original instance's accepted status.

venkatrea696188

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 .

keerthik0010Author

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?

stefanhelzle0001

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.

keerthik0010Author

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.

stefanhelzle0001

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.

keerthik0010Author

Hi Stefan,

thanks for response.

Using process report. Tasks which user member of specific groups and also if he is manager. He is manager of both tasks.

mikes0011Answer

Brainy

Pass the username of the previous user into the Manager Review task. You won't be able to disable the "accept" button, but you can do on-form checks to check whether the task's viewer is the same as the previous user, and display a validation message alerting them that they are not allowed to perform that review.

Then they could either use the OOB "reject" button or, as a special case, you could build a custom Submit Button saying something like "send back to reviewer group", which would simply exit the task and loop immediately back to it allowing the original group assignment to take hold again regardless of the original instance's accepted status.

keerthik0010Author

Thanks Mike, I had same thoughts if OOTB not possible to disable the buttons.

I had implemented the same, it works for business.

Sign up

Login with SSO

Login to the community

Login with SSO