Hi all,
I have a scenario where a related action opens a pop-screen for users input. If user hits the back button the pop-up goes away but the instance is active in backend, and on hitting the related action again it creates a new instance. Is there any way by which the instance is cancelled on hit of back from browser.
Discussion posts and replies are publicly visible
For this record action, do you use the process start form or an initial user input task in the process model?
Its an activity chained UIT
Do you have a specific reason for that design decision? A record action using this design will automatically start that process instance. If the use navigates away, you have to issue of orphaned process instances. Try to use a start form. That way the process is only started as the user submits the form.
There are certain business logics to be made before getting the UI. Hence went with the said approach.
Would it be possible to execute that business logic in an expression and call it in the record action config? Then feed the results into the process start form?
Thats a good suggestion for implementing a start form, but the form that is part of the related action is conditional, user may or may not face it.
One thing which I am thinking of is to get the process id of previous active instance and cancel them.
Before trying to solve the problem, I suggest to prevent it. Try that first!
One option is to follow the pattern described in my blog post: appian.rocks/.../
This looks good and should serve the purpose buddy. Thanks