Unlike scenarios, workflows do not have to be enabled or disabled within the ATG Control Center in order to make them active or inactive. As long as the Web application that uses them is running, workflows are started whenever an event occurs that represents the beginning of a workflow (for example, an employee clicks the Submit button for his or her expense report). This behavior is in contrast to the startup behavior of scenarios. When you start the Scenarios module, all enabled scenarios are started and begin waiting for their specified events to occur.
Note for developers: The event that represents the beginning of a workflow must trigger the workflow by calling the StartWorkflow method of the WorkflowView object associated with this event. See the Javadoc for atg.workflow.WorkflowView in the ATG API Reference.
