Berto2002 Posted May 18 Share Posted May 18 I have a BPM that Resolves a Request and then a node that waits for a Customer Update before proceeding through the BPM. If no Update, it expires and closes. If there is an update, it should go back around the main BPM flow. If the Customer rejects the Resolution, they need to put comments and these go on the Timeline as an Update with visibility of Customer.; but those Updates don't trigger the BPM node to proceed which they should do. If the Customer adds another Update on the Request, the node does react; so it seems to be missing a trigger for the Update which is part of the rejecting the Resolution action. from the Link to comment Share on other sites More sharing options...
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 account
Already have an account? Sign in here.Sign In Now