...
Prior to Version 3.3, when a new workflow definition was implemented in production, any in-progress live instances were automatically updated on deployment to adhere to the new workflow design. This had the potential to lead to complications with existing in-flight workflows if the cut-over was not carefully handled.
To Provide choice and control over workflow changes, V3.3 implements a new process to detach prevent in-flight workflow instances from automatically adopting the latest FAB workflow changes introduced in production. By default, existing instances in production will maintain their original workflow definition as assigned at the time of submission (creation of the instance), ensuring inflight in-flight workflows can complete without interruption or update. Similarly, new instances will seamlessly automatically adopt the most recent available workflow definition, maintaining consistency across the project lifecycle. Lastly, the ability for prior instances to be updated to the latest version is made available in the Instance data FAB Data report.
Auto-Versioning (FAB v3.3)
...
| Info |
|---|
When no Workflow Version is activated yet for the Project Form Application, the Workflow Instance ID (/IQX/FAB_WF-MD5_CHECKSUM) will be on its fall-back set to the “fallback” value: Form Instances submitted for WF Versions with Editable status will have this fall-back fallback value as their unique MD5_CHECKSUM. |
...