Workflows enable you to automate Adobe Experience Manager (AEM) activities. Workflows:
Consist of a series of steps that are executed in a specific order.
Can interact with assets in the repository, user accounts, and AEM services.
Can coordinate complicated activities that involve any aspect of AEM.
The business processes that your organization has established can be represented as workflows. For example, the process of publishing website content typically includes steps such as approval and sign-off by various stakeholders. These processes can be implemented as AEM workflows and applied to content pages and assets.
For further information see:
Workflow models in AEM are the representation and implementation of business processes:
When a workflow model is started (executed), a workflow instance is created. A workflow model can be started multiple times, each time generating a distinct workflow instance. For each instance, the steps that the workflow model defines are executed.
The steps performed are those defined by the workflow model at the time the instance is generated. See Developing Workflows for further details.
Workflow instances progress through the following lifecycle:
The workflow model is started and a workflow instance is created and running.
The first step of the workflow model is executed.
The step is completed and the workflow engine uses the model to determine the next step to execute.
The subsequent steps in the workflow model are executed and completed.
When the final step is completed, the workflow instance is completed and therefore archived.
Many useful workflow models are provided with AEM. In addition, the developers in your organization can create custom workflow models, tailored to the specific needs of your business processes.
When workflow steps are executed, they are associated with a workflow instance. The history of a workflow instance includes information about each step that has executed for the instance. This information is useful for investigating problems that occur during execution.
Either a user or a service performs workflow steps, depending on the type of step:
If an error occurs, the service/step implementation should handle behavior for an error scenario. The workflow engine itself will retry the job, then log an error and stop the instance.
A workflow can have one of the following status:
RUNNING: The workflow instance is running.
COMPLETED: The workflow instance has been successfully ended.
SUSPENDED: Marks the workflow as suspended. However, see the Caution note below on a know issue with this state.
ABORTED: The workflow instance has been terminated.
STALE: Progression of the workflow instance requires that a background job executes, however the job cannot be found in the system. This situation can occur when an error occurs when executing the workflow.
When the execution of a Process Step results in errors, the step appears in the administrator’s Inbox and the workflow status is RUNNING.
Depending on the current status, you can perform actions on running workflow instances when you need to intervene in the normal progression of a workflow instance:
Marking a workflow state to “Suspend” has a known issue. In this state it is possible to take actions on suspended workflow items in an Inbox.