workflow-model-design

Design and deploy AEM 6.5 workflow models with step types and variables.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill workflow-model-design-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-model-design
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/workflow-model-design
Command: npx skills add https://github.com/valithedge/etisalatedge --skill workflow-model-design-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AEM teams often need to design and deploy robust workflow models to automate content processes, coordinate human tasks, and ensure consistent deployments across environments.

Core Features & Use Cases

  • Define step types (PROCESS, PARTICIPANT, DYNAMIC_PARTICIPANT, OR_SPLIT, AND_SPLIT) and configure their properties.
  • Declare workflow variables and transitions, map deployment storage (/conf or /etc) and runtime location (/var/workflow/models).
  • Use the Workflow Model Editor or content packages to design, test, and deploy end-to-end workflows for authoring, review, and publishing.

Quick Start

Open the Workflow Model Editor, create a new model under /conf/global/settings/workflow/models, and deploy via Package Manager or Maven to /var/workflow/models.

Frequently Asked Questions about workflow-model-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an AEM 6.5 workflow model with AND_SPLIT and OR_SPLIT steps?

You can design AEM 6.5 workflow models by defining step types like PROCESS, PARTICIPANT, AND_SPLIT, and OR_SPLIT in the Workflow Model Editor. Configuring transitions and variables ensures robust routing before deploying to /conf or /etc.

What is the correct JCR path structure for deploying AEM workflow models?

The correct JCR path structure for AEM workflow models involves storing designs under /conf or /etc and syncing to the runtime location at /var/workflow/models. This ensures models conform to 6.5 LTS guardrails during deployment.

Can I deploy AEM workflow models using Maven content packages?

Yes, you can deploy AEM workflow models using Maven content packages or the Package Manager. This approach packages the model XML and JCR path configurations to ensure consistent deployment across different AEM environments.

When should I use a DYNAMIC_PARTICIPANT step versus a standard PARTICIPANT step in AEM workflows?

Use a DYNAMIC_PARTICIPANT step when the workflow assignee must be resolved at runtime via an external selector, whereas a standard PARTICIPANT step assigns a specific user or group. Both step types help automate human tasks within AEM workflow models.

Do I need to know model XML to design AEM workflows?

Yes, designing AEM workflows requires knowledge of model XML and JCR paths to ensure proper structure and deployment. This knowledge guarantees the model design conforms to 6.5 LTS guardrails when syncing to /var.

AEM workflow model deployment not working, what are the limitations or guardrails?

AEM workflow model deployment limitations often involve failing to sync models to /var/workflow/models or ignoring 6.5 LTS guardrails. Ensure your deployment targets the correct JCR paths under /conf or /etc to avoid runtime errors.