Workflow Launchers Skill — AEM as a Cloud Service

To auto-start AEM workflows on content changes, configure Workflow Launchers that listen for JCR events. Define the eventType, glob, nodetype, and workflow path to trigger the Granite Workflow Engine automatically upon modifications.

A cq:WorkflowLauncher is a configuration node that maps JCR events to workflow execution. It specifies the eventType, nodetype, and glob path to trigger a designated workflow automatically when matching content changes occur.

Deploy custom workflow launchers by creating configurations under /conf/global/settings/workflow/launcher/config and deploying via your Cloud Manager pipeline. This approach overrides out-of-the-box behavior without modifying /libs.

Yes, you can trigger workflows for DAM assets and page content using common launcher patterns. Configure launchers targeting dam:AssetContent for assets and cq:PageContent for pages to automate processing on modifications.

Fine-tune AEM workflow launchers at runtime by controlling run modes and exclude lists. Enable or disable specific launchers to manage what content triggers workflows and prevent unintended automated executions.

A key constraint is avoiding modifications to /libs. Overlay and override out-of-the-box launcher behavior by deploying custom configurations under /conf/global/settings/workflow/launcher/config to ensure changes persist.