Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

During roll out of new Workflow definition, the Previously, when a new workflow definition was implemented in production, any in-progress instances submitted previously will now follow beforehand were automatically updated to adhere to the new workflow design. This could cause issues on uncompleted and missed tasks and may result However, this transition could lead to complications, especially with incomplete or missed tasks, due to discrepancies between the workflow definitions, potentially resulting in broken instances.

To counter address this problemissue, we shall allow implemented a new process to isolate in-flight workflow instances to be isolated from the latest FAB workflow changes rolled out introduced in production. Old Existing instances in production shall continue to use the WF Definition in the point of time it was submitted. In the same mannerwill maintain their original workflow definition at the time of submission, ensuring continuity. Similarly, new instances will automatically use the latest workflow definitionseamlessly adopt the most recent available workflow definition, maintaining consistency across the project lifecycle.

Auto-

...

Versioning (FAB v3.3)

Changing the workflow definition automatically increments the WF version.

To deactivate this feature, follow these steps: https://iqxbusiness.atlassian.net/l/cp/QuU2TqTU

Revised Versioning (FAB v3.3.1)

With the introduction of Non-Breakable Workflow design in FAB version 3.3, any modifications made to workflows in development now automatically trigger versioning. This results in the creation of a new workflow version each time changes to the WF definition are saved. While this ensures version control, it presents challenges during the development and testing phases where numerous modifications and test instances are expected.

Moreover, tracking and monitoring the specific workflow version used at the time a form instance was created has become difficult.

To address these issues, we have enhanced the revision process for workflow versions. We have introduced a new API to collect the deep structure of revision fields and to facilitate workflow version control for in-flight form instances.

Below is the relational deep structure from the Project App level to the Workflow Version level.

...

Description

Table Field

Project Form App

In every Project Form App, there may exist multiple Form Iterations.

ZFORM_NAME

Form Iteration

Each Form Iteration can accommodate multiple Workflow IDs intended for future Alternate Workflows. Form Iteration value increments whenever user saves the form app via 'SAVE (new iteration)' button or form is transported through systems.

ZITERATION_NO

Workflow ID

Since the Alternate Workflow functionality has not been released yet, Workflow IDs as of FAB released v3.3.1 will consistently remain set to '1'.

ID

Workflow Version

Within each Workflow ID, numerous Workflow Versions can be found, each possessing a unique HASH character identifier.

All workflow versions available for each Form App can now be easily viewed via the new workflow designer. See Version List

VERSION_ID

Related Tables

  • /IQX/FAB_WF - FAB Enhanced Workflow Definition

    • Adds new line for every new Project App-Form Iteration-WF ID-WF Version combination

    • Features:

      • WF instance

      • Multiple workflows per Project

      • Default workflow

      • Traceability - fields MODIFIED_*

    • Repurposed Fields:

      • ZITERATION_NO: incrementing, to be used as WF Version

      • ID: to be used as WF ID

      • ZID: to be used as WF Description

    • New Fields:

...

Field

KEY

Type

Description

ZWF_INSTANCE

PK

HASH160

WF Instance (MD5)

ZFORM_NAME

FK

CHAR 24

FAB Project ID

ID

FK

NUMC 6

Workflow ID

ZITERATION_NO

FK

NUMC 6

Workflow Version

ZDEFINITION

 

STRING

WF Definition in JSON

Other related objects

For list of technical objects affected by this change, see https://iqxbusiness.atlassian.net/wiki/spaces/IPM/pages/2159542343/Design+of+non-breakable+WF+for+in-flight+FAB+instances?atlOrigin=eyJpIjoiM2Q4NDk3OTY0NDNlNDcxY2FhOWFlZGY0ZjQ3YTMzNTEiLCJwIjoiYyJ9 .