Martyn Houghton Posted January 6, 2020 Share Posted January 6, 2020 The current 'Wait for Request Update', is only applicable to the first update made to the request in its lifespan. If the suspend node in is used in the BPM process after a single request update has already been made, it will not suspend. As such, support confirmed this is working as designed, so is only really useful for pausing new requests at the beginning of the workflow. Therefore this is a enhancement request to provide a new suspend option 'Wait for New Request Update', which will suspend the node at any point in the BPM and irrespective of whether there has been previous request updates and await a NEW update being made. As with the other suspend nodes, this should also include the expiry period option. Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted January 6, 2020 Author Share Posted January 6, 2020 @Paul Alexander I suspect this is the same issue you had under your post below. Cheers Martyn Link to comment Share on other sites More sharing options...
Guest Paul Alexander Posted January 6, 2020 Share Posted January 6, 2020 Hi @Martyn Houghton Yup...that sounds like it's exactly the same problem. As mentioned in my request there IS some investigation ongoing about creating a new node which WILL wait for a NEW request update. thanks Link to comment Share on other sites More sharing options...
James Ainsworth Posted January 6, 2020 Share Posted January 6, 2020 There is a defect record in our system for this. It doesn't suggest that we will be creating a new Hornbill Automation, but rather adding a fix or option to the existing one. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted January 7, 2020 Author Share Posted January 7, 2020 @James Ainsworth Thanks. Can you let me know the PM number for the defect? Cheers Martyn Link to comment Share on other sites More sharing options...
James Ainsworth Posted January 7, 2020 Share Posted January 7, 2020 The fix for this issue has been completed and is expected in the next Service Manager update which should be available in the next week or two. Regards, James 1 Link to comment Share on other sites More sharing options...
Guest Paul Alexander Posted January 8, 2020 Share Posted January 8, 2020 Great news @James Ainsworth. thanks. 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