How Flowable engine takes versioning of forms while displaying

1

How is Flowable engine decide which form version to choose?

While designing the process in modeler, we inject form key and form reference in the properties pane of user task.
After which we deploy the process and start new process instances.
Now, even if we make changes to form after the previous deployment and make new app deployment, the previous process instance takes the old version which was present at the the time of deployment and the same with latest forms and latest deployment.
How is it tracking the versioning details without version being injected while creating a new process definintion?

2 Likes
2

Any insights here? I’m having the exact same problem. I’m using a form with multiple versions and when I deploy the process definition, my user task is not showing the most updated version of the form with matching formKey. How can I make my user task point to the latest version?

3

How did you deploy the forms? How are you using the forms? Flowable Task or your own UI?