- Comience ya
- Mejores prácticas
- Capacidades
- Aptitudes
- CLI
- Ejemplos
- Resumen de ejemplos
- Receta: crear un agente
- Receta: automatizar con RPA
- Receta: introducir datos en una aplicación web
- Receta: extraer datos de una aplicación de escritorio
- Receta: refactorizar y probar un flujo de trabajo
- Receta: un proceso basado en colas con REFramework
- Receta: crear un Maestro Flow
- Recipe: build a Maestro Case
- Receta: aplicación codificada y flujo de trabajo de API
- Recipe: build a coded function
- Receta: extraer datos de documentos con IXP
- Avanzado
- Ayuda
Case Management applications for long-running, exception-heavy work about a specific situation, such as a claim, a dispute, or a loan application, built with phased validation and human review gates.
A Maestro Case orchestrates long-running, exception-heavy work about a specific situation — a claim, a dispute, a loan application — through stages, tasks, and business rules until it resolves. With a coding agent, you describe the case, review a decision-first design packet, and the agent builds a runnable caseplan.json, then helps you validate, publish, and run it.
Lo que creas
A Maestro Case moves a single case instance through stages, each holding the tasks that need to happen while the case is in it. It suits work that is unpredictable and long-running rather than a fixed sequence: a dispute that might escalate, pause, or reopen; a claim that needs different reviewers depending on its value.
What a case is built from
- Stages and tasks — the tasks inside each stage, referencing existing tenant resources or built as new API workflows, agents, or human-in-the-loop steps in the same solution.
- Transition rules — the conditions that move a case forward: entry, completion, exit, and re-entry rules written from your business policy.
- SLAs and escalations — a duration a case or stage is allowed to run, and what happens when it's breached, such as escalating to a supervisor.
El ciclo de vida completo
| Estado | Qué hace tu agente de codificación | Ejemplo de solicitud |
|---|---|---|
| Diseño | Proposes the case's stages, tasks, rules, and SLAs from your description, and shows you one decision-first review before building anything. | Configura un caso de resolución de disputas con etapas e hitos. |
| Crear | Authors and validates the case definition (caseplan.json) from the approved design. | Build it — pause at the mid-build preview so I can check it in Studio Web. |
| Publicar | Publishes to Studio Web for a visual preview, and to Orchestrator when you're ready to run it live. | Publish this case to Studio Web. |
| Depurar | Runs the case for real against live connections, on your explicit approval. | Run a debug session for this case with a sample claim. |
La habilidad detrás de esto
This work is powered by the uipath-maestro-case skill, which authors Case Management applications with phased validation. It hands the design step to the uipath-planner skill when no design document exists yet, then builds, validates, and publishes the case once you approve the design. You can see it in the Skills catalog.
Una solicitud de inicio típica
Una primera solicitud podría tener este aspecto:
"Set up a dispute-resolution case with stages and milestones: intake, investigation, and resolution, with an escalation to a supervisor if investigation runs longer than three business days."
The agent proposes the full design — stages, tasks, rules, and SLAs — for your review before it builds anything.
Más solicitudes para probar
- Build a loan-application case with stages for intake, credit check, underwriting, and decision, routing to manual underwriting when the automated credit check is inconclusive.
- Add an escalation rule so a case notifies a supervisor if it's in the investigation stage for more than two business days.
- Publish this case to Studio Web so I can preview it before it goes live.
Profundizar
For the full picture of Case Management, see Build a Maestro Case with a coding agent.