Redeploying an unchanged BPM model doesn't pick up form changes

I’m following the tutorial at:
Getting started with Human Task Orchestration | Camunda Platform 8

I deployed the model for choosing a dinner dish. After doing that I discovered that I had a typo in my form. I had specified one of the select values as Salid/salid instead of Salad/salad.

I corrected the mistake in my form, and redeployed that BPM model, thinking that the new deployment would pick up the form change. This did not appear to the case. The dropdown, still showed a “Salid” instead of “Salad”.

How can I trigger redeployment so that the new select value is displayed?

Hi @Chuck_Irvine,

If you mean for a running process instance, then that cannot be changed after it is started. Because the form is embedded in the process definition, it is “baked in” to the process instance.

New instances of the process will use the modified form for user tasks.

HTH,
Josh

1 Like

Hi Josh,

No, I wasn’t referring to an existing running process. This happened after deployment of a new process definition and for a process instance created after the deployment.

From what you say, this isn’t the expected behavior. Maybe I’ll try again to make sure. Thanks

Charles