Understanding Workflow Steps

Or Split

Example: In a content approval workflow, after the initial review by the content manager, the workflow encounters an “Or Split” step. This step evaluates whether the content meets specific criteria. If the content meets the criteria (e.g., passes a plagiarism check), it proceeds to the next step for final approval. If it doesn’t meet the criteria, it triggers a notification to the author to make revisions.

AND Split

Example: In a document publishing workflow, the “AND Split” step is used to ensure that multiple conditions are met before proceeding. For instance, before publishing a document, the workflow checks if it has passed both the legal review and the compliance review. Only if both conditions are met does the workflow proceed to the publishing step.

Lock Payload Process

Example: In a collaborative document editing workflow, the “Lock Payload Process” step prevents concurrent editing conflicts. When a user begins editing a document, the workflow locks the document’s payload to prevent others from editing it simultaneously. Once the editing is completed and the user releases the lock, others can access the document for editing.

Unlock Payload Process

Example: Building upon the previous example, the “Unlock Payload Process” step is triggered when a user finishes editing a document. It releases the lock on the document’s payload, allowing other users to access and edit the document without conflicts.

Set Variable

Example: In a customer support ticketing workflow, the “Set Variable” step stores relevant information about the ticket, such as the ticket ID, customer details, and issue category, into variables. These variables are then used throughout the workflow for routing the ticket to the appropriate support team, updating the ticket status, and generating reports.

Goto Step

Example: In a content approval workflow, let’s consider a scenario where a document fails initial review due to missing metadata. The “Goto Step” step can be used to redirect the workflow back to the metadata entry step, allowing the user to update the necessary metadata fields. Once the metadata is updated, the workflow resumes from the point of failure, ensuring that the document meets all requirements before proceeding to the next stage of the approval process.

Delete Node

Example: In a content deletion workflow, the “Delete Node” step removes specific content nodes or assets from the AEM repository. For example, after a content expiration date is reached, the workflow automatically deletes outdated content nodes to maintain a clean and organized content repository.