Giuseppe Iannacone Posted February 27, 2019 Author Share Posted February 27, 2019 @Victor just to double check you are reffering to: so if this is true can be tested on a live (failing process) doing the change you are suggesting? i expect the affected one to be closed automatically. or this has to be done for each process which is currently using the wrong flowcode? thank you Link to comment Share on other sites More sharing options...
Victor Posted February 27, 2019 Share Posted February 27, 2019 @Giuseppe Iannacone - follow the advice given by James regarding editing a process instance and make the change on a current workflow that is in a suspended state (wait for the status change). Once the node expires, it should follow the "expired" route (the "reopen" route will no longer be accessible because of the new expression) If you like to make this change on workflows associated with ongoing requests, then yes, you will have to make this change to all of them... of course only if they fall into the scenario I described otherwise they will be fine. Until a different solution is available I would say to make this change on BP configuration so all new requests will have the change already... Link to comment Share on other sites More sharing options...
James Ainsworth Posted March 4, 2019 Share Posted March 4, 2019 Hi @Giuseppe Iannacone We have added a check that will clear this variable that was causing your issue each time the Suspend and Wait for Status Change was reached. This should allow you to maintain your original configuration without having to change all of your BPMs. This will be available as of the next Service Manager update (build 1453) I hope this helps. Regards, James Link to comment Share on other sites More sharing options...
Giuseppe Iannacone Posted March 7, 2019 Author Share Posted March 7, 2019 On 3/4/2019 at 6:36 PM, James Ainsworth said: Hi @Giuseppe Iannacone We have added a check that will clear this variable that was causing your issue each time the Suspend and Wait for Status Change was reached. This should allow you to maintain your original configuration without having to change all of your BPMs. This will be available as of the next Service Manager update (build 1453) I hope this helps. Regards, James @James Ainsworth thank you, really appreciated Link to comment Share on other sites More sharing options...
Giuseppe Iannacone Posted September 30, 2019 Author Share Posted September 30, 2019 @Victor & @James Ainsworth sorry to bother you again but it seems like our 2 stage closure is not working properly, can you please attach a bpm sample so I can adjust mine according to your suggestions? 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