Create, pack, debug, validate, and author Case Management projects using `uip maestro case`, the third Maestro orchestration surface alongside BPMN and Flow.

uip maestro case creates, packs, debugs, and authors Case Management projects — a third Maestro orchestration surface alongside BPMN and Flow. A case project models a long-running, human-driven unit of work as a case plan: a JSON document (caseplan.json) describing stages, tasks, SLAs, triggers, and the entry/exit conditions that move a case between stages — closer to a structured workflow-with-a-lifecycle than a linear process.

The tool ships as the separate @uipath/case-tool package, dynamically loaded by @uipath/maestro-tool under the case branch — every command here is invoked as uip maestro case <verb>, never as a standalone uip case.

Create a new Case project with boilerplate files: project.uiproj, operate.json, entry-points.json, bindings_v2.json, package-descriptor.json, and a minimal caseplan.json (only written if one doesn't already exist — re-running init never clobbers an authored case plan). If run outside an existing solution, a parent <name>Solution is scaffolded automatically and the case project is nested inside it; if run inside one, the project is registered into that solution instead.

CasePlanStatus is "Created" on a fresh scaffold or "Preserved" when an existing caseplan.json was left untouched (re-running init on a project you've already authored). SolutionRegistration is always present — its Status is "NotInSolution" rather than the field being omitted when no parent solution exists.

Pack a Case project directory into a .nupkg file, reading caseplan.json from the project root.

Also accepts this repo's shared package-metadata options (--repository-url/--repository-commit/--repository-branch/--repository-type, --release-notes, --project-url, --author, --description) — see any other pack command's Options table (for example uip maestro bpmn pack) for the full shared set, which this command registers identically.

A schema error during packing (a malformed caseplan.json) is enriched with case-specific guidance before being surfaced as a failure — expect actionable Instructions, not a raw parser error.

Debug a case project by uploading it to Studio Web and running a debug session there — there is no local-only debug mode for Case Management (unlike some other Maestro debug commands).

Requires an active login (uip login) with a resolvable organization, tenant, and access token — fails fast with a specific message naming whichever piece of login state is missing.

Keys are kept in their native camelCase (not PascalCased) — this payload is designed to be read programmatically by eval checkers and SDKs, matching the same carve-out used by Flow's debug command and registry get. The command exits non-zero when finalStatus is anything other than "Completed"/"Successful", even though the envelope itself reports Result: "Success" — check the exit code, not just the presence of Data, in scripts.

Validate a case management JSON file against Case Management's structural and business rules.

Omitting all four runs the default full profile: lenient, so partially-authored or already-packed files still validate.

Profile: "strict" is added to Data only when --strict (or --sdd) was passed. On a run with none of the profile options, when an sdd.md is found next to the case plan or at the root of its solution, Data.Suppressed ({ Profile, Sdd, Errors, Warnings }) counts the strict and SDD findings the default profile does not show, and Instructions gives the --strict --sdd command that shows them. Warnings/Issues are present only when the valid file still produced warnings. On failure (Result: "Failure", exit 1), Data.Issues carries every error and warning with a stable Code, Path, Message, and Severity — parse this array rather than the human-readable Instructions text if you're driving a repair loop.

Rewrite a case plan JSON file in place, pretty-printed with a 2-space indent and one key per line, so a file-edit tool can patch it.

Data shape: Code: "CaseFormat", Data: { Changed, Lines, LongestLine }.

Derive bindings_v2.json from a case plan and write it in the same directory as the plan, overwriting an existing file. The file is required by uip solution resources refresh for solutions authored without Studio Web. The command reads only the case plan and the entry-points.json file next to it.

Data shape: Code: "CaseBindingsSync", Data: { BindingsPath, ResourceCount, ConnectionCount }.

Read a Solution Design Document (sdd.md), the document that validate --sdd audits a case plan against.

Write a task's inputs, outputs, and context into a case plan from a saved result, without calling a tenant.

Data shape: Code: "ConnectorShapeSpliced" with --spec, or Code: "DescribedIoApplied" with --described. With --spec, Data is { Path, Summary }, where Summary holds TaskId, TaskType, ServiceType, ContextEntries, Inputs, Outputs, ConnectionBindingId, FolderBindingId, and BindingsReused.

Generate a normalized ConnectorTaskSpec — everything needed to construct a runnable Integration Service activity or trigger task inside a case plan. Looks up the type in the local TypeCache, lists Integration Service connections for the connector, and fetches Integration Service metadata.

A trigger spec's operation shape differs (eventMode/event name instead of an HTTP verb/path) — see the second example above.