TBuyukkilic | 2024-05-26 20:22:41 UTC | #1
Please see original post, haven't gotten a reply: https://developer.genesys.cloud/forum/t/cannot-route-using-agentassignmentalerting-when-assigneeid-is-set/25220
The solution is to remove the assignee then to perform this action, however removing the assignee just doesn't work from Architect. I've managed to send a NOT_SET to an action which should set the assigneeId to null, but then I get a 403 error that doesn't make any sense:
Note that his is an old error:
- REST call for action execute failed. Message: Request to backend service failed. Response from web service: {"message":"Unable to perform the requested action. Assignee must have at least one of the following permissions assigned: [workitems:workitem:view, workitems:workitem:edit, workitems:workitem:delete] in at least one of the following division(s): xxx","code":"assignee.missing.any.division.permissions","status":403,"contextId":"xxx","details":[],"errors":[]} [xxx]
Updating the assigneeId to null via API works fine, but not via Architect/actions.
system | 2024-06-25 20:19:45 UTC | #2
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 26470