samwoo Posted June 4, 2018 Posted June 4, 2018 Hello, I have a need to change our BPM's Closure stages this week and i've just shockingly found out that I cannot reopen tickets back to the team who resolved it in the first place. I've been trying different things to get this working and I cannot. Whenever a call gets resolved, the Custom Field - O gets updated with the team that resolved the ticket, before being reassigned to the Service Desk queue. Using the Wait for Status change node, we can detect whether a customer or analyst has reopened the ticket. BUT the team that resolved the ticket could be different to the team that picked it up in the first place, and we really really need a way to reassign a re-opened ticket back to the team that resolved it (Custom Field O). Can something be done to provide this quickly? Is there a change to add this in that could be bumped up rather quickly if not difficult to implement? Or is there something I can do already within the BPM? I've tried the node...Application: Hornbill Service ManagerScope: ApplicationType: AssignTask: Assign RequestTeam (Manual): &[global["flowcode"]["customFieldO"]] But this doesn't even work, despite allowing a flowcode input... Please help! Samuel
Victor Posted June 7, 2018 Posted June 7, 2018 I believe @Martyn Houghton was requesting something very similar and (iirc) we have a change for this... @Steven Boardman?
Martyn Houghton Posted June 7, 2018 Posted June 7, 2018 @Victor, @samwoo I think this is the one you are referring to Victor, which is along the similar lines, but on the assign to most available analyst/round robin nodes where there is not even the option for a variable. However like Sam we would want to be able to use variables in these nodes to save on hard coding decision trees in the BPM. I think the point here is that thought the 'Application' scope BPM Nodes where being deprecated in favour of the 'Entity' ones, but the replacement 'Entity' scope ones do not have the option for variables,which was present in the former. Cheers Martyn
samwoo Posted June 8, 2018 Author Posted June 8, 2018 Hi @Victor and @Martyn Houghton, Thanks for responding - yes I would like the ability to use a variable to re-assign a ticket back to the resolving team (with the option under the same action to reassign it back to the resolving Owner, should a particular service require it). Thanks, Samuel 1
Dan Munns Posted June 25, 2018 Posted June 25, 2018 @samwoo are all your support teams under the same parent organisation? I ask because I have a feeling the output to custom O field will output the team name as say "Service Desk" but the assign to team probably uses the team name as BUSINESS/IT_Networks/IT_Service_Desk/ with the preceding main business and parent department (as least it used to show as this if selected in a BPM) If all your support teams are under the same department (IT for example) if you put BUSINESS/IT/&[global["flowcode"]["customFieldO"]] it might work? Worth a try perhaps.
samwoo Posted October 31, 2018 Author Posted October 31, 2018 Reviving this thread Any further updates to being able to use a Variable to assign teams? I haven't had an opportunity to look at what @Dan Munns has suggested yet though. Thanks, Samuel 1
Martyn Houghton Posted November 20, 2018 Posted November 20, 2018 @James Ainsworth, @Victor Is there any update on being able to use variables to assign teams using the different assignment operations include round robin? Cheers Martyn
James Ainsworth Posted November 20, 2018 Posted November 20, 2018 Hi @Martyn Houghton No progress on this yet. I'll review the change again and see where it currently sits. I'll update this post once I know more. Regards, James
Martyn Houghton Posted November 21, 2018 Posted November 21, 2018 @James Ainsworth Thanks. It if can be prioritised, as at the moment we have to setup multiple decision nodes within the BPM to hard code assignment nodes so the correct team value is used. Cheers Martyn
Guest Ehsan Posted November 21, 2018 Posted November 21, 2018 @Martyn Houghton, This is being investigated. Unfortunately it's not a quick turnaround, as introducing an option to automatically populate Team option may impact Assign to Owner (Variable) Automated Task, which will be considered a change in behaviour given that some Business Process designers may set the Team option to Auto rather than Ignore. We may have to go down the route of providing a new Automated Task to allow a Business Process designer to set the Team option using the Variable Picker. We'll report back once when we have determined the route we're going to take to get around this. Ehsan
James Ainsworth Posted July 31, 2019 Posted July 31, 2019 @samwoo We are currently working on adding the ability to assign to a team using a variable. Could you let me know what the format is that you are using for the team. We need to know if the variable should be based on the display name of the team or the ID. We are not sure which one you are storing. Regards, James 1
samwoo Posted July 31, 2019 Author Posted July 31, 2019 10 minutes ago, James Ainsworth said: @samwoo We are currently working on adding the ability to assign to a team using a variable. Could you let me know what the format is that you are using for the team. We need to know if the variable should be based on the display name of the team or the ID. We are not sure which one you are storing. Regards, James Hi @James AinsworthAinsworthAinsworthAinsworth, Many thanks for this. We are currently storing the display name of the team, though I could understand if the team name changes it could have an impact on being able to reassign the ticket. If there could be an ability to check if the assign to team using variable has failed I could branch off to re-assign to a default team using ID. Thanks again, Samuel
James Ainsworth Posted July 31, 2019 Posted July 31, 2019 Thanks for the reply @samwoo. We had actually written this using the display name but I just wanted to check as I didn't want to deliver this and get it wrong. It has some final tests to go through then you should see it within a couple of Service Manager releases. I'll try to update this post once it is available. James 1
samwoo Posted July 31, 2019 Author Posted July 31, 2019 2 minutes ago, James Ainsworth said: Thanks for the reply @samwoo. We had actually written this using the display name but I just wanted to check as I didn't want to deliver this and get it wrong. It has some final tests to go through then you should see it within a couple of Service Manager releases. I'll try to update this post once it is available. James Thanks James, I look forward to this.
James Ainsworth Posted October 4, 2019 Posted October 4, 2019 Hi Samuel, I just wanted to let you know that this is now available as of Service Manager build 1667. Documentation can be found here. Hope this helps. Regards, James 1
Jeremy Posted November 4, 2021 Posted November 4, 2021 Sorry to drag up an old thread, but we are using a teams drop down in a human task (Problem management checks) and we are having problems assigning to a 'team via a variable' in the timeline it suggests that it is exporting: urn:sys:group:siteam Which is our SI Team but when we take this from the human task and enter into the variable field to assign it just skips the step and doesn't actually assign to the chosen team. We have tried putting into a custom field and again this still does not assign. Is there something that we are doing wrong? This is the BPM This is where we choose the team: This is the node where we 'assign' to the team:
samwoo Posted November 4, 2021 Author Posted November 4, 2021 Oh, that's interesting - I have a similar problem that I've not yet received a response for... but for me, it's assigning the Human Task to a Team using a Variable... maybe these two issues are similar? Definitely something that needs to be addressed 1
Jeremy Posted November 5, 2021 Posted November 5, 2021 @samwoo maybe we have this is in two processes our problem and known error ones, but it WORKS in the Problem one it's just the Known Error one that refuses to assign even through the process for that bit are exactly the same....it's annoying me at the moment as we are trying everything we can think of to try to fix it.
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