Hi,
We have an approval process for our Service Requests in which Portal Customers can set approvers themselves from the Service Desk Portal. Right now, we have have restricted the workflow to disallow the "approve / reject" step where Approver = Reporter. However, the user can still create the ticket, which means it is stuck in limbo in the "Waiting for Approval" status unless we create an automation that informs the user after creating the ticket that they need to set an appropriate approver.
Is there a way (through Forms, Custom field configuration, workflows or Portal configuration) to limit the User Picker (multi) for Approvers such that you cannot set currentUser() or similar from that field, so that the Portal users are not able to create a ticket when Approver = Reporter?
Thanks
If anyone found this thread and is looking for automation to handle this issue, here is what we have implemented (Triggers on Value changes for Approvers):
If:
If Approvers contais only themselves ( {{issue.approver.size}} = 1) as approver, @-mentions Reporter and transitions issue to New. If themselves AND someone else
( {{issue.approvers.size}} > 1), Advanced Edit only removes Reporter and keeps status "Waiting for Approval".
Here is the snippet for Advanced Edit to remove Reporter only from Approvers (or any other Multi User Picker custom fields):
{
"update": {
"Approvers": [{ "remove": { "accountId":"{{issue.reporter.accountId}}" } }]
}
}
As of now, there is no feature out-of-box that you can configure the scenario you have.
The solution you already applying (via automation) is the one available.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi and thanks for your answer. After searching a bit, I came to the same conclusion myself, but always worth checking if someone has another workaround. Hopefully there will be a better way to handle this in the future.
Kim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.