cmmn-create_task
cmmn-create_taskCreate a CMMN task with lifecycle states, decision support, and automated sentry triggers for case management workflows.
Instructions
Creates a CMMN-aligned task with lifecycle state management
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| auto_complete_on_sub_case | No | Automatically complete this task when sub-case completes (default: true) | |
| assigned_to | No | Who/what is responsible (user, agent, system) | |
| title | Yes | Task title/summary | |
| required_evidence | No | Evidence-key names the agent must supply on completion (e.g. ['migration_file_path', 'test_file_path']). Optional. | |
| estimated_hours | No | Estimated effort in hours | |
| context | No | Working notes, reasoning, approach for AI resumption | |
| decision_type | No | How to evaluate: expression, table, ai, external | |
| required | No | Is this task required for parent stage auto-complete? Default: true | |
| process_definition_id | No | Process definition ID to execute (for task_type='process') | |
| output_mapping | No | Map sub-case results back to parent task (keys are parent field names) | |
| case_model_id | No | CasePlanModel ID to instantiate when task becomes active (only for task_type='case') | |
| triggers_sentry_on_outcome | No | Map of outcome values to sentry IDs. When decision produces an outcome, triggers corresponding sentry. | |
| decision_expression | No | Expression to evaluate (for decision_type='expression'). Supports: 'amount > 1000', 'status == approved', 'count in [1, 2, 3]' | |
| exit_criteria | No | Conditions that must be met to complete (legacy free-form list — use acceptance_criteria for judge-layer verification) | |
| entry_criteria | No | Conditions that must be met to start | |
| input_mapping | No | Map parent case data to sub-case (keys are sub-case field names) | |
| input_data | No | Input variables for the process (for task_type='process') | |
| sub_case_name | No | Name for the sub-case (defaults to task title if not specified) | |
| task_type | No | CMMN task type: human, process, case, decision | |
| case_id | Yes | Case ID (@rid format) | |
| due_date | No | Target completion date (ISO8601) | |
| description | No | Detailed task description | |
| priority | No | Priority: critical, high, medium, low | |
| status | Yes | CMMN lifecycle state: available, enabled, disabled, active, suspended, completed, terminated, failed | |
| decision_description | No | Natural language description (for decision_type='ai'). AI will evaluate and return outcome. | |
| created_by | No | Who created this task | |
| parent_id | No | Parent item ID (for hierarchical nesting) | |
| next_steps | No | Planned next actions | |
| blocked_by | No | What is currently blocking this task | |
| decision_table | No | Decision table rules (for decision_type='table'). Array of {conditions: {var: val}, outcome: 'result'} | |
| acceptance_criteria | No | Judge-layer acceptance criteria. Each item is {id, text, verifier}. verifier is a registered check name (schema_check, file_exists, command_runs_clean, ...) or 'manual'. Workflow author attaches these so the runtime judge can evaluate task completion claims. | |
| decision_inputs | No | Input variables for decision evaluation. Keys are variable names, values are the data. | |
| depends_on | No | Task IDs this task depends on | |
| auto_complete_on_decision | No | Automatically complete this task when decision is made (default: true) |