Versions Compared

Old Version 4

changes.mady.by.user Hannah.Dela

Saved on

compared with

New Version Current

changes.mady.by.user Hannah.Dela

Saved on

Key

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

When upgrading to FAB version 3.3.1 or higher, it is required to use the Process Designer version 2 with two-column layout. The following activities must be completed to implement the new Process Designer:

Activation

Check/Activate the new process designer via transaction SICF.

...

Configuration

Update FAB Configuration to point to the new Process Designer. This may be done via transaction /IQX/FAB_CONFIG → Editors. URL pattern is as follows:

  • If you want to use the on-premise UI5 version: https://<sapserver:port>/sap/bc/ui5_ui5/iqx/process_edit2/index.html

  • If you want to specify the UI5 version to be 1.71 (from the SAP Cloud repositories): https://<sapserver:port>/sap/bc/ui5_ui5/iqx/process_edit2/index_1_71.html

  • If you want to specify the UI5 version to be 1.120 (from the SAP Cloud repositories): https://<sapserver:port>/sap/bc/ui5_ui5/iqx/process_edit2/index_1_120.html

...

  • Ensure that the updates in /IQX/FAB_CONFIG are correct for both the Back end and Front-end systems. Failure to do so may result in the display of the outdated Process Designer layout, accompanied by missing workflow definitions.

  • Please also exercise caution when configuring for a system with two clients: one for development and another for testing. If the The client systems are not must be properly linked, this setup may result to avoid resulting in unwanted creation of new workflow versions each time the new Process Designer is opened.

Post Upgrade Tasks for Existing Applications

After activating and switching to Process Designer version 2, please proceed with the post-upgrade tasks for existing applications. IQX developers are ready to assist you with this process.

To ensure a smooth transition between versions, redeploy existing FAB Form applications with configured workflows. This will create a new version in the Workflow Version List and initiate the new FAB Process Flow. Use the matrix below to determine the specific cutover steps required.

  1. Review existing FAB Form applications

  2. Redeploy FAB Form applications

FAB Form App in the DEV/QAS

Post Upgrade Task

Without existing changes in development/testing

  1. Add the PRD version to a customizing transport request (TR).

  2. Release the customizing TR from DEV to PRD to create a new workflow instance for every system the TR is imported to.

With existing changes in development/testing

  1. Export the form app (UI only) and workflow in DEV/QAS to a local file to back up the current changes in development/testing.

  2. Roll back the DEV version using the PRD version by exporting the form app (UI only) and workflow from PRD and importing it into DEV.

  3. Add the PRD version to a customizing transport request (TR).

  4. Release the customizing TR from DEV to PRD to create a new workflow instance for every system the TR is imported to.

  5. Re-import the current changes in development/testing in DEV/QAS using the backup file downloaded in step 1.

3. Validate new workflow versions

More Information

FAB Process Flow Version Comparison

Workflow Data Comparison Across FAB Versions