Search the Community
Showing results for tags 'await expiry'.
Can I request the addition of a 'Seconds' column to the 'Expire period', as there as cases when trigger BPM actions we need to suspend for a shorter period of time than 1 minute. This is especially true when under taking integration actions and also action after other suspend nodes where the BPM process has been resumed but simultaneous operations occurring on the request have not been committed to the database which result in the BPM retrieving on incorrect data. For example we have a process which awaits the request coming off hold which is followed immediately by a get request details and decision node. We have had occurrences where the request has been taken off hold by an update on the customer portal and the BPM has resumed but the full update from the portal has not completed/committed so the subsequent decision node does not have the up to date information and branches incorrectly. Cheers Martyn Note: the above scenario was discuseed with @Victor as part of IN00158237
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