Martyn Houghton Posted November 14, 2019 Posted November 14, 2019 As per of a investigation with Hornbill support (IN00158425) the Suspect - Await Expiry is applying some form of Working Time Calendar even though it does not have the WTC options the other hold/suspend processes do,. We when using the suspend node and the BPM resumes out of hours, the node will suspend not for the duration of the expiry there and then but hold until the WTC starts and then commences the timer to suspend. Cheers Martyn
Martyn Houghton Posted November 18, 2019 Author Posted November 18, 2019 As per the post below, this node is suspending based on the default working time calendar, rather than the one linked to the the actual Service Level Agreement.
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