Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Reference  
  Search  |  Index  
Concepts
  About attachments
  About the Component Integrator
  About launching a workflow
  About milestones
  About operations
About the RMI registry
About rosters
About routing
About rules
  About security
  About security queues
  About step processors
  About step states
  About system maps
  About transfer
  About workflow fields
  About workflow maps
  About workflow participants
  Component queue security issues
  Content Engine (CE) operations
  Coordinate information
  Custom web applications
  Eliminating port 32771 conflicts
  Java Runtime Environment (JRE)
  Maximum index key size
  Naming conventions
  System fields
  Troubleshooting
  Wildcards
  Workflow database field size limitations
  Workflow exceptions
Events & Statistics
Expressions
Procedures
   

About transfer

Before a workflow can run, an executable version of the workflow definition must exist in the Process Engine database. Saving a workflow definition in Process Designer does not accomplish this; instead, this action occurs via the transfer process.

There are several ways to initiate a transfer:

  • In Process Designer
    • You can directly transfer a workflow definition to the Process Engine using the File/Transfer command.
    • When you launch a workflow from Process Designer, the Launch Workflow tool both transfers the workflow definition and starts the process defined on the workflow map(s).
  • In Workplace
    • You can directly transfer a workflow definition to the Process Engine. See Transfer a Workflow Definition in online Help for Workplace under Tasks/Manually launch a workflow.
    • When you define a subscription, a transfer will occur automatically if the version of the workflow does not already exist in the Process Engine database. See Create or Edit a Subscription in online Help for Workplace under Tasks.
  • In FileNet Web Services Client and Open Client
    • When you define a link between a workflow definition and a document or document class, a transfer will occur automatically if the version of the workflow definition does not already exist in the Process Engine database. See the online Help for Linker.

As part of the transfer process, the workflow definition is validated. The validation process checks for errors such as incorrect expression syntax and invalid routing conditions. Any errors encountered during validation must be corrected before the transfer can occur. In addition, transfer cannot complete if the executable version of a workflow definition exceeds 512K for an Oracle database or 64K for a Microsoft SQL Server database (see "Miscellaneous Problems" in the Help for Process Engine Administration for further details).

Similarly, system configuration settings defined in the Process Configuration Console (including definitions of queues, rosters, and event logs) must be transferred to the workflow database. In the Process Configuration Console, the Commit Changes action transfers any unsaved changes you have made in the current Process Configuration Console session.