PluginPublic

adobe/aem-cloud-service

All AEM as a Cloud Service skills: component development, Workflow model design, development, triggering, launchers, debugging, and triaging, Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening, Rapid Development Environment (RDE) deployment, log inspection, snapshots, and troubleshooting via `aio aem rde`, Jackrabbit Oak query/index tuning (property, Lucene index definitions), and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quick Start Guide — AEM Workflow Development (Cloud Service)

Determine What You Need

User request
    ├── "How do I create a workflow model?"
    │       → workflow-model-design/SKILL.md
    │
    ├── "How do I write a custom process step / participant chooser?"
    │       → workflow-development/SKILL.md
    │
    ├── "How do I start a workflow programmatically / via API?"
    │       → workflow-triggering/SKILL.md
    │
    ├── "How do I auto-trigger a workflow when content changes?"
    │       → workflow-launchers/SKILL.md
    │
    └── "I need end-to-end help designing + building + deploying a workflow"
            → workflow-orchestrator/SKILL.md

Minimum Viable Workflow (3 steps)

Create a model XML at /conf/global/settings/workflow/models/my-workflow/jcr:content/model
Implement a WorkflowProcess class registered with process.label=My Step
Deploy via Cloud Manager pipeline (model in ui.content, bundle in ui.apps)

Prerequisite Checklist

Before starting:
- [ ] AEM Cloud Service SDK installed locally
- [ ] Maven project with ui.apps + ui.content modules
- [ ] Service user configured (or use existing workflow-process-service)
- [ ] Bundle deployed and process.label visible in Workflow Model Editor

Verify Deployment

# Check OSGi bundle active
curl -u admin:admin http://localhost:4502/system/console/bundles/<bundle-name>.json

# Verify process.label registered
curl -u admin:admin "http://localhost:4502/libs/cq/workflow/admin/console/content/models.json"

# Check model synced to /var
curl -u admin:admin "http://localhost:4502/var/workflow/models/my-workflow.json"

Start a Test Workflow via API

# POST to /var/workflow/instances — NOT /api/workflow/instances (posting there silently
# writes stray JCR nodes and returns a misleading 2xx without starting any workflow).
# Returns HTTP 201 with an HTML body linking to the new instance path.
curl -u admin:admin -X POST \
  "http://localhost:4502/var/workflow/instances" \
  --data-urlencode "_charset_=utf-8" \
  --data-urlencode "model=/var/workflow/models/my-workflow" \
  --data-urlencode "payloadType=JCR_PATH" \
  --data-urlencode "payload=/content/test-page"

# Confirm it is running
curl -u admin:admin "http://localhost:4502/var/workflow/instances.RUNNING.json"

Monitor at: Tools → Workflow → Instances → filter by model or status.