Summary
During roll out of new Workflow definition, the in-progress instances will follow the new workflow design which could cause issues on uncompleted and missed tasks, resulting in broken instances.
As alternate workflow is introduced, this problem will be solved by allowing in-progress workflow instances to be isolated from the latest FAB workflow changes. Old instances in production will continue to use the WF Definition in the point of time it was created. In the same manner, new instances will automatically use the latest workflow definition.
Related Tables
/IQX/FAB_WF - FAB Enhanced Workflow Definition
Repurposed fields to support features:
WF instance - fields ZDEFINITION, MD5_CHECKSUM
Multiple workflows per Project - incrementing ZITERATION_NO
Default workflow - IS_DEFAULT
Traceability - fields MODIFIED_*
/IQX/FORMHD_INST - FAB Form Header Instance Data (run-time values)
/IQX/FAB_WF_INST - FAB - Enhanced Workflow Instance (New Table)
To store the definition snapshot of WF Definition when a FAB instance is submitted.
Add Comment