Martyn Houghton Posted May 23, 2022 Share Posted May 23, 2022 There seems to be an issue with Update Request > Place on Hold node. When specifying a value in the 'On Hold Period', in this case 6 in the month field, it actually puts the request on hold for 6 minutes! 1st screenshot is from the BPM and the second is from a request which has passed through the node. Not sure if this is relevant but this is on a Known Error request type. Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted May 23, 2022 Author Share Posted May 23, 2022 From doing some different combinations, it appears you have to fill in the unit values in order for the node to apply the correct units to the hold period. Link to comment Share on other sites More sharing options...
James Ainsworth Posted May 31, 2022 Share Posted May 31, 2022 Hi Martyn, Thanks for posting this and great to see that you have found a workaround. I've reported this back to the development team. Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2022 Share Posted May 31, 2022 On 5/23/2022 at 1:51 PM, Martyn Houghton said: it appears you have to fill in the unit values in order Just to clarify, if I fill the numbers in right-to-left (i.e. starting with the minutes) then it won't apply correctly even with a valid value? Link to comment Share on other sites More sharing options...
James Ainsworth Posted June 1, 2022 Share Posted June 1, 2022 Hi Martyn A change has been put in place to prevent this from happening. This will be available in the next Service Manager update. 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