gwynne Posted June 6, 2018 Share Posted June 6, 2018 Hello I cant seem to assign a ticket to the request creator in the BPM without specifying a team manually, is there a reason the auto function does not work is there a way around auto assigning to creator without specifying this? G Link to comment Share on other sites More sharing options...
Victor Posted June 6, 2018 Share Posted June 6, 2018 @gwynne let's say the creator is a member of more than one team... what team is the BP supposed to assign to then? Link to comment Share on other sites More sharing options...
Martyn Houghton Posted June 6, 2018 Share Posted June 6, 2018 @Victor We too use this node. At the moment the BPM Node does not allow you to pass a variable into the 'Team' parameter, so you have to hard code it in the BPM. Also I not sure what logic the 'Auto' option applied as we have never been able to get this method to work. Can a feature request be raised to allow the use of a variable for the 'Team' parameter and perhaps advise on what logic is applied when the Auto option is used. Cheers Martyn Link to comment Share on other sites More sharing options...
gwynne Posted June 6, 2018 Author Share Posted June 6, 2018 I do agree with that, however limiting the selection to one team means I have to create a much larger workflow for the sake of people in different teams to use it. could it not be based one what team supports the service or a node / variable checking the service for the supporting team and doing a match with the creator? Link to comment Share on other sites More sharing options...
Victor Posted June 6, 2018 Share Posted June 6, 2018 1 minute ago, Martyn Houghton said: Can a feature request be raised to allow the use of a variable for the 'Team' parameter I think this is already on the list as it been requested previously... 2 minutes ago, Martyn Houghton said: what logic is applied when the Auto option is used. for this particular node, none... the node interface is generic (so to speak), it does not sort of "tailor" on very specific aspects or scenarios of a node... Link to comment Share on other sites More sharing options...
Victor Posted June 6, 2018 Share Posted June 6, 2018 Just now, gwynne said: could it not be based one what team supports the service or a node / variable checking the service for the supporting team and doing a match with the creator? again, what if this check returns more than one team? what if the service is supported by two or more teams and the creator is a member of two or more of these? I know I sound like the devil's advocate here, just trying to explain the rationale. I do agree that configuration can be improved and sometimes is not very straight forward but there are challenges that we cannot overcome easily... and this requires more thought.. Link to comment Share on other sites More sharing options...
gwynne Posted June 6, 2018 Author Share Posted June 6, 2018 hehe dont worry about it, appreciate that its not straight forward, just want to put so you guys can at least think about potential solutions. thanks for responding G Link to comment Share on other sites More sharing options...
Victor Posted June 6, 2018 Share Posted June 6, 2018 @gwynne we are thinking of it I just wanted to make you aware of the predicament we are currently in regarding this functionality... Link to comment Share on other sites More sharing options...
Guest Posted June 7, 2018 Share Posted June 7, 2018 @gwynne @Martyn Houghton Hi both, We do actually have an alternative to creating a brand new team for everyone that currently exists in the tool. If you use a combination of the "Get Request Information" automated task, and then the Assignment automated task selecting the option Assign to Owner (variable) this allows you to not have to specify a support team as mandatory and set the Owner to be a variable of your choice - so in this case you would use the "Created By" info that was picked up by your Get Request Information node. The way this will work is that it will always assign the request to the creator, but against the first support team it finds for them in the DB. So if they are a member of 10 support teams, it will automatically pick the first one. Then, the owner can choose to manually reassign it to themselves in a more appropriate team if they desire, but it means the request will at the least be assigned to the correct persons. Some screenshots on how to set this up: Link to comment Share on other sites More sharing options...
Victor Posted June 7, 2018 Share Posted June 7, 2018 I learn something new every day Link to comment Share on other sites More sharing options...
Claire Holtham Posted June 7, 2018 Share Posted June 7, 2018 I have this exact issue. So essentially if I specify the Owner, but not the team it won't entirely wig out with the red message of doom, it will pick something and carry on. For the users I have in mind they are all only members of one team... Link to comment Share on other sites More sharing options...
Guest Posted June 8, 2018 Share Posted June 8, 2018 Hi @Claire Holtham That's right you won't get an error using the approach specified above. But if everyone is part of the same team anyway, you are better off using our standard "Assign to Creator" node and specifying the team name. Kind Regards Bob Link to comment Share on other sites More sharing options...
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