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 processed by one of the following:
Routes between the steps indicate one or more possible processing paths.
Each workflow definition has a main map (called Workflow) with a Launch step that executes when the workflow is launched. For a simple workflow, you can place all of the workflow steps and routes on this map. For a more complicated business process, you can place the steps for the primary process on the main map and use submaps for secondary processes. A single step (Submap 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.