create-workflow

Add workflow_instance and workflow_state fields to the collection, create a workflow_json definition in daas_wf_definition, then link them with a daas_wf_assignment row. Finally add the WorkflowButton component to your UI so users can execute transitions.

Create a policy, link it to the role via daas_access, and add the resulting access UUID to the command's policies array in workflow_json. Users holding any listed policy can run that command; empty policies mean anyone with write access can.

The workflow_instance field is missing the special: ["m2o"] meta attribute, so the system does not recognize it as a relation to daas_wf_instance. Update the field meta to include special: ["m2o"] and confirm the assignment row uses the workflow field name.

The old field must be hidden and its required flag dropped, since DaaS cannot delete field metadata via MCP. Then migrate all consumers such as badges, filters, and archive props to workflow_state, or item creates will fail with 400 errors.

Supported patterns include simple draft/published, content review with approve and reject, multi-level approval chains like manager then director review, and version-based workflows where each content version carries its own workflow state.