Before a workflow can run, it must be transferred to the Process Engine database to convert it to an executable format. If you use the Launch command to launch a workflow from Process Designer, the transfer occurs. You can also manually transfer a workflow definition to the Process Engine using the procedure below. See About transfer for additional information.
NOTES
If you launch the workflow definition or workflow collection from Process Designer, checkin, validation and transfer run automatically before the workflow launches unless you disable checkin and validation in the Preferences dialog box (Settings menu).
You can validate and transfer workflow definitions or workflow collections in both PEP format and XPDL 2.0 format. Since an XPDL file can contain more than one workflow definition, you can specify which workflow definitions are to be validated and transferred using Workflow Properties > Advanced.
During the transfer process, Process Engine checks for errors in the current workflow definition or specified workflow definitions in the collection. While you can disable validation in Process Designer (Setting > Preferences), it is somewhat easier to resolve errors detected by the Validate command in Process Designer, because the validation results provide links to the step or route with the problem. If Process Engine detects errors during transfer, Process Engine provides a list of the errors but you must use Process Designer to find and fix them.
Saving a workflow definition either locally or in an object store preserves the user-editable workflow definition, but does not make it executable.
To transfer the specified workflow definitions in the workflow collection
On the Process Designer File menu, click Transfer Workflow Collection.
If Add/Check In Before Transfer/Launch is enabled in Settings > Preferences, you must add or check in the workflow collection to your object store before it is transferred to Process Engine.
To transfer the current workflow definition
On the Process Designer Action menu, click Transfer Workflow.
You will not be prompted to add the workflow definition to your object store because the workflow definition is part of a collection.
Any errors will be displayed in a Validation Results window. Select each item (usually a step) from the Name list to see a description of the error. All errors must be resolved before the transfer is successful. See Validation results for additional information.
TIPS
If any step in the workflow definition references a step processor that does not exist on this system, you must open that step and select a step processor from the list. This situation can occur if the workflow definition was defined on a different system or if a step processor was deleted after it was referenced in the workflow definition.
Validation does not report as an error an empty F_Trackers workflow group or a step where the participant is not assigned because trackers and participants can be specified as part of the launch or, for the participant, any time before the step is executed.
If you transfer from Process Designer and the workflow definition is checked out, the vwversion property on the Library/object store item will be updated. If the document is not checked out or the user does not have the right to check in the document, the property will not be updated.
If you have access rights that allow you to use the Configuration option in Process Designer, you can create queues, rosters, and event logs with access granted to specific users. For example, only UserA can use a certain queue or roster. If you use this queue for a step destination or you specify the roster for this workflow definition, you will get a validation error because you do not have rights to this queue or roster.