Hello everyone :)
is it possible to move a ticket to another workspace and then adding the previous agent as a watcher?
I didn’t see an option to do that nor does the workflow automator seem to allow this.
We’ll have agents for each workspace and they’re supposed to be confined in their respective workspaces; so straight up giving them access to the other workspaces is unfortunately not an option for us.
edit:
In the workflow automator we can set an action to add specific watchers to the ticket after it is moved to another workspace, but we need it to auto-pick the agent that originally grabbed the ticket.
Solved
Moving tickets to other workspaces and the visibility for the previous agent
+2Best answer by robertromario
Hi Yooji,
Maybe the below solution can help.
1, Create a custom dropdown field, for example: Event performing user and make it as a data source with agents.
2, Create a workflow automator with the below configuration.
Event:
Web request (Node 2):
You can find the API field name for the custom field using this API call - Service Desk API for Developers | Freshservice
You can find the placeholders for event performing agent ID in the “insert placeholder” option - above the body field.
I would suggest using “?bypass_mandatory=true” at the end of the endpoint URL which will help execute the API call without any errors like missing a mandatory field.
3, Action:
I am using the placeholder of the custom field (which currently holds the agent's name who updated the workspace field) as the watcher value.
+1Hi Yooji,
Maybe the below solution can help.
1, Create a custom dropdown field, for example: Event performing user and make it as a data source with agents.
2, Create a workflow automator with the below configuration.
Event:
Web request (Node 2):
You can find the API field name for the custom field using this API call - Service Desk API for Developers | Freshservice
You can find the placeholders for event performing agent ID in the “insert placeholder” option - above the body field.
I would suggest using “?bypass_mandatory=true” at the end of the endpoint URL which will help execute the API call without any errors like missing a mandatory field.
3, Action:
I am using the placeholder of the custom field (which currently holds the agent's name who updated the workspace field) as the watcher value.
Freshworks Implementation partner | robert.romario@saasgenie.ai
+14Good one, sad there are no way to remove :(
Solution consultant @ synerity.eu, A new error is always a sign of progress!
1 person likes this
Reply
Join the Community
Already have an account? Login.
Sign in to the Community
No account yet? Create an account.
Social Login
Login with LinkedInor use your username
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.