Migrating EPX Process Flows and Subflows – Active Work Items - Precisely_EnterWorks - EnterWorks - 11.0

If the target EPX server already contains the Process Flows and Subflows being migrated, and there are active work items in the Process Flows in the target EPX that need to be retained and completed, then the old versions of the workflows cannot be deleted from the target EPX prior to the migration of the new versions. While EPX has a work item transfer utility that is intended to transfer work items from the old versions of the workflow to the new, it is not functional. Instead, the recommended strategy is to allow the existing work items to complete their processing in the old version of the workflow (while preventing any new work items from being created) and have all new work items be created in the new version of the workflow.

If the nature of the changes to the workflow are such that the existing work items need to have the changes apply to them, then it will be necessary to manually update the workflows in the target EPX instead of migrating the workflows. The Compare Extract Script for EPX can be used to ensure that all of the changes in the source have been made correctly in the target.

If the current work items can complete their processing in the old version of the workflow, then migrate the new EPX workflows by performing the following steps:

1. Open the EPX Design Console and log in as user system.
2. Expand the Process Modeling->Process Flows and Process Modeling->Subflows folders.
3. Compile a list of process flows to be migrated. If a subflow needs to be migrated, include all process flows that call the subflow:

   Workflow	Description
   <list of workflows to be migrated>

4. Pause EPX processing.
5. For each process flow and subflow in the above list, perform the following steps:
   1. Right-click the Process Flow or Subflow and select Open from the pop-up menu.
   2. Add " OLD" to the end of the Name for the Process Flow or Subflow.
   3. Click the Process Flow Modeler tab.
   4. For each starting point manual activity in the workflow:
      1. Double-click the activity (or right-click the activity and select Properties from the pop-up menu).
      2. Click the Details tab.
      3. Select the Select… button.
      4. Select a user from the list that is not active in EPX (create a user if necessary). This effectively disables the old workflow, preventing any users from creating work items for it.
      5. Click OK.
      6. Click OK.
      7. Repeat the above steps for any additional starting point manual activities
   5. Click Save.
   6. Repeat the above steps for each process flow/subflow in the list above.
6. Select the menu option Tools->Import/Export menu option (if the option is disabled, click the EPX_<server> entry in the navigation tree first). The Import/Export Utility window appears:
   
7. Click the Migration Source button. The Migration Source prompt appears.
8. Select EPX Import File for the Source and click the … button.
9. A file browser appears. Select the EPX workflow zip file generated from the source EPX and click Open.
10. A Migration Source window will open. Click OK:
11. The EPX Migration file is loaded into the Source window:
    
12. Expand the Process Flows and Subflows folders
13. Click each process flow and/or subflow and click the single right-arrow button. The Process Folder appears in the Destination list:
    
14. Click the Migration Destination button. The Migration Destination prompt appears.
15. Click Migrate. The Two workflows are re-created. Eventually a Collision Error prompt appears.
16. Click Skip All. The migration processing completes.
17. If any of the workflows or subflows invoke the Email BIC activity and the target EPX has different mail server requirements (such as DEV does not use SLS or TLS security but PROD does):
    1. Edit the workflows containing the Email BIC activity
    2. Modify each Email activity.
    3. Change the security on the Outbound settings to SSL or TLS
18. Stop and restart all EnterWorks Services