bug? Update Request > Place on Hold - On Hold Period not applying correct duration - asked for 6 months got 6 minutes

[Martyn Houghton]

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

 

[Martyn Houghton]

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.

 

[James Ainsworth]

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.

[Steve Giller]

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?

[James Ainsworth]

Hi Martyn

A change has been put in place to prevent this from happening.  This will be available in the next Service Manager update.