Files
Akanksha Jain 4517c39bb4 fix(aem-workflow): correct workflow-triggering skill for Cloud Service (#180)
Validated against Granite workflow source (com.adobe.granite.workflow.api,
com.adobe.granite.workflow.api.it.http) and a live AEM instance.

HTTP Workflow API:
- Root the API at /var/workflow/instances; warn that POST to
  /api/workflow/instances writes a stray JCR node and returns a misleading
  2xx without starting a workflow (clean GET there returns 404)
- Document start (201 + <a id=Location>), JSON detail fields, state-selector
  listing, and suspend/resume/terminate via state= POSTs

Programmatic API:
- Use WorkflowSession.terminateWorkflow() (terminate() does not exist)
- Use Workflow.State.RUNNING.name() (Workflow.STATUS_RUNNING does not exist)

Service user:
- Map a subservice to a service user that is a member of the
  workflow-process-service group (a group, not a user); add repoinit example

Manage Publication:
- Note the payload is a JCR_PATH to the package node under
  /var/workflow/packages (not the individual pages) for payload debugging

Co-authored-by: akanjain <akanjain@adobe.com>
2026-06-12 17:12:25 +05:30
..