HHH Posted September 26, 2018 Share Posted September 26, 2018 Hi When creating a new BPM I use the Automated ATsk node to set status and sub status for a certain type of ticket. However the node does not allow me to set status to "on hold" When I set the sub status (which is an on hold) substatus and leave the status field to Auto, the BPM crashes. Link to comment Share on other sites More sharing options...
Steven Boardman Posted September 26, 2018 Share Posted September 26, 2018 @HHH have you tried using the Request > Update Request > Place on Hold option? this includes the sub-status setting? Steve Link to comment Share on other sites More sharing options...
HHH Posted September 26, 2018 Author Share Posted September 26, 2018 That's a workaround we can use until the status node works fully. Link to comment Share on other sites More sharing options...
HHH Posted September 26, 2018 Author Share Posted September 26, 2018 @Steven Boardman Hi Steven, that did not work at all. Status is still open and no sub status is set. Link to comment Share on other sites More sharing options...
Steven Boardman Posted September 26, 2018 Share Posted September 26, 2018 @HHH in the place on hold option it does require either the On Hold Period or the On Hold Until fields to carry a value / variable - in these cases it then functions as expected. If you don't want to put this on hold for a time / period then using the update status option is the correct one. I have just tested the update status option and have the On Hold option available and also selected a sub status This correctly put my request on hold for an undefined period. Are you on the latest build of service manager? Steve Link to comment Share on other sites More sharing options...
HHH Posted September 26, 2018 Author Share Posted September 26, 2018 @Steven Boardman I'm on build 1335, shall I put this to the support portal? Link to comment Share on other sites More sharing options...
Steven Boardman Posted September 26, 2018 Share Posted September 26, 2018 @HHH if you are not seeing the On Hold status in the update status drop down then that might be the best course of action as it seems to be behaving as expected and visible on my instances Link to comment Share on other sites More sharing options...
Victor Posted September 26, 2018 Share Posted September 26, 2018 @HHH - most likely reason why you don't see the "On Hold" status in the list when configuring the node is that the simple list, used to populate the values there, does not have this value... Please have a look at the simple list to see if the value is there and if not add it. Then try again in the node configuration. P.S. - The "correct" way to do this would be to use the "Place On Hold" dedicated node as the list had the value removed for this reason. You can add it in the interim to have your node working but is a temporary solution. 1 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