Mike Hillman Posted September 5 Posted September 5 I feel like I'm likely missing something obvious with this one, so if I am I seek forgiveness in advance! We use Custom Buttons to allow Service Desk staff to assign tickets to themselves - an Assign to Me button essentially The button runs an Auto Task which assigns the ticket to a specific user - I currently have 15 separate Auto Tasks created, one for each member of the team, each of which is hardcoded to assign the ticket to that specific user (via the Assign to Owner node) and 15 separate Custom Buttons which are set to display to each of the users using the Session > User field under 'Show Button If....' and are each set to run the appropriate Auto Task for the user it displays to My question is, is there a way in the Auto Task workflow to pick up the Session User (I.e. the agent who is logged in and clicking the button) so I can set the owner of the ticket to this - that way, I only have to have one Auto Task and one Custom Button, and it will assign the ticket to whoever is logged in and clicks it I am aware there is now the Take Ownership option which does essentially do this, however I also use the Auto Task to do a few other things for reporting purposes, so would prefer the team to use this rather than the Take Ownership link
Peter Clough Posted September 5 Posted September 5 We user to have a task for this, setting the owner to &[global["session"]["userId"]] in the autotask worked. Though when I went to find what we were using, that showed as being a variable that didn't exist, so you might need to tinker a bit with it.
EWA Posted September 5 Posted September 5 Wouldn't it be the same variable as the one use for replies within a request. It adds the name of whoever is replying from within the request.
James Ainsworth Posted September 5 Posted September 5 Hi Mike, As @Peter Clough described, there is a global session variable that can be used. However, the autotask workflow presents a warning (circled in red) as this variable sits outside of the workflow engine and the validation doesn't recognize it. You can still save it and it should work for your purpose.
Mike Hillman Posted September 6 Author Posted September 6 that's all perfect, thanks all! I've given it a go using the variable and it's working well, so that'll make life a lot easier! Thanks again 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now