A customer created a workflow launcher to trigger the "Custom Workflow" based on "Node Created" under the folder /var/classes, but the workflow is not triggered.
What is the reason the workflow is not triggered?
A.
"Workflow Process Legacy Mode" is disabled at the "Adobe Granite Workflow Configuration Service" OSGi configuration.
B.
AEM does not allow new nodes to be created under /var/classes.
C.
Changes under /var/classes do not trigger workflows.
Workflow launchers in AEM are designed to monitor changes in specific repository paths such as /content, /content/dam, and /conf. However, changes under certain system-level paths, including /var, do not trigger workflows. This restriction is intentional, as /var is used for system-generated and internal data such as workflow instances, audit logs, and temporary nodes. Triggering workflows on changes under /var could result in recursive or unintended behavior. Option A is unrelated because Workflow Process Legacy Mode refers to backwards compatibility. Option B is incorrect, as AEM does allow system nodes under /var, but they are not workflow-launcher enabled. Adobe documentation makes clear that workflow launchers must be configured under supported content paths for them to execute correctly.
[Reference: AEM 6.5 – Workflow Launchers, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit