Understanding JD Edwards EnterpriseOne Workflow Process Transfers

You must be careful when promoting JD Edwards EnterpriseOne workflow processes through the development cycle. JD Edwards EnterpriseOne workflow processes are transferred by Object Management Workbench (OMW) much like any other non-OMW object. However, a key difference is that instances of the modified process version may already be running in the target environment. Because of the wide range of changes that can be made while editing a workflow process version, it cannot be guaranteed that the old instances will be able to complete under the new definition.

For example, if you delete a task from the JD Edwards EnterpriseOne workflow definition and an instance in the target environment is currently executing the task, the instance will not be able to determine what to do next once the task is completed. In a similar manner, all the historical data used for analysis can become invalid if the process is changed dramatically before it is transferred.

To keep this type of problem from occurring, it is recommended that you never modify a workflow process version that has been promoted and used in the target environment. Instead, make a copy of that version; edit, test and promote it; and then deactivate the current version and activate the new version. OMW helps enforce this by not allowing you to transfer a workflow process version into an environment if any historical instances of that particular version exist in the target environment.

The same types of problems can occur if you are using a particular process version and you receive and deploy an update to that version. This problem can be avoided if you do not use delivered versions of JD Edwards EnterpriseOne workflow processes. Instead, always make a copy of the JD Edwards version and activate your copy.

In OMW, workflow data transfer is accomplished with object transfer activity rules. Consequently, you must add workflow processes which need to be transferred from one environment to another to an OMW project.

Your system administrator usually sets up object transfer activity rules. These rules dictate the source and target locations for transferring objects and, in the case of workflow processes, these values correspond to data source names. The rules are executed when a project is advanced from one status to another. The same transfer rules apply regardless of the logon environment.