Migrating In-flight Workflow Applications

This topic describes how an agency users migrate in-flight permit and license applications from an earlier workflow version to a newly activated workflow version within the same Gen3 environment by using Manage Workflow Applications page.

Permit and license applications are associated with a specific workflow process definition and version in OCI Process Automation (OPA). When workflow logic is updated and a new workflow version is activated, newly submitted applications use the updated workflow, while applications that are already in progress continue to run on the earlier version. Use the Migrate In-flight Process Instances option in the Manage Workflow Applications page, to identify in-flight applications and migrate them, so they continue processing with the latest activated workflow.

Using the Manage Workflow Applications Page

From the Fusion Application Permitting and Licensing home page, navigate to Manage Workflow Application page by selecting Workflow Instances.

Follow these steps to search for in-flight workflow applications that are eligible for migration.

  1. Select Source Workflow Application ID from the drop-down list by identifying the workflow of in-flight applications you want to migrate.

  2. You can optionally enable Select by Application Type option to filter search to narrow the list further by Application Type.

  3. Click Search to view the in-flight workflow applications that are eligible for migration.

  4. Review the list of applications and information available for each application.

    The following table describes information shown for each in-flight application.

    Page Element

    Description

    Application ID

    Displays the workflow application ID associated with in-flight applications.

    Application Type

    Displays the application type based on selected Source Workflow Application ID.

    Classification

    Indicates whether the application is a permit or license.

    Current Process Definition

    Shows the workflow process currently used by application.

    Current Version

    Displays the workflow version the application is currently running on.

    Target Version

    Displays the newer activated workflow version available for migration.

    Total Applications

    Shows the total number of in-flight applications eligible for migration under selected workflow.

    Selected Applications

    Shows the number of applications selected for migration.

    Action

    Allows you to view individual application details in a drawer at the right.

  5. Select the applications you want to migrate and click Migrate. This starts in-flight migration to the target workflow version.
  6. To track migration jobs, use the Migration Status button.
Note: You cannot perform in-flight migrations for major workflow changes such as removal of required steps or activities, deletion of events, or changes to routing logic that cannot be reconciled in the OCI Process Automation (OPA).

Scheduling In-flight Migration Jobs

You can run a migration job right away or schedule it for later from the Process Monitor page on the agency springboard. If there are many in-flight applications, it is usually better to schedule the job during non-working hours so active users and processes are not affected.

Migration runs as an ESS job. While scheduling it, you can set a duration (in hours) to control how long the job runs in one go. For example, setting the duration to 6 hours allows the job to run for six hours and migrate as many applications as possible in that time. If some applications are still left, the next scheduled run automatically continues the migration and picks up the remaining applications.

To schedule an in-flight migration, open the Schedule New Process drawer and select Migrate Public Sector Active Applications Workflow option. For more details about scheduling and tracking these jobs, see Using the Process Monitor.

Viewing Details of In-flight Migrations

You can use the Migration Status page to view a list of migrated in-flight applications.

The following table describes information shown for each migration job.

Page Element

Description

Application ID

Identifies the workflow applications for which in-flight applications were migrated.

Application Type

Displays the permit or license application type associated with the workflow.

Classification

Indicates whether the workflow applies to permits or licenses.

Current Process Definition

Displays the workflow process definition used before migration.

Current Version

Shows the workflow version used by in-flight applications before migration.

Target Version

Shows the workflow version used after migration.

Status

Displays the overall migration job status, such as in Progress, Completed, or Completed with Errors.

Selected Applications

Shows the number of applications selected for migration.

Total Error

Displays the number of applications that failed during migration.

Job Start Date

Shows the date and time when the migration job started.

Job End Date

Shows the date and time when the migration job completed.

Actions

Allows you to view details in a drawer for applications included in the selected migration job.

Note: The Application ID on the Migration Status page represents the source workflow, while the Application ID in the drawer represents an individual application.