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 workflow maps

A workflow map is a graphical representation of a workflow that shows the sequences of steps needed to complete the business process. Each step represents a specific activity that will be performed by one of the following:

  • One or more workflow participants.
  • An automated process.
  • One or more system functions, such as BeginTimer.

Routes between the steps indicate one or more possible processing paths.

Submap step on main map calls specified submap

Each workflow definition has a main map (called Workflow) that executes when the workflow is launched. Generally, you can place all of the workflow steps and routes on this map. For a more complicated business process, place the steps for the primary process on the main map and use submaps for secondary processes. A single step (calling step) on a map calls a submap. When processing of the steps in the submap is complete, control returns to the calling step.

Another advantage to using submaps is that you can call a submap from any map within the workflow definition. If a submap defines a process you want to execute multiple times, you can call the submap when needed, rather than defining the process in multiple places.

In addition to workflow maps defined by the workflow author, there are system maps that the system software executes automatically under certain conditions. Generally, it is not necessary to modify these system map. For further information see About system maps.