- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Special project settings for Studio Web solutions containing multiple interrelated projects such as agentic processes, RPA workflows, decision rules, and apps.
A solution in Studio Web can contain multiple interrelated projects—such as Maestro agentic processes, RPA workflows, decision rules, apps, and more. Some of these projects serve specialized roles that extend or support your agentic process execution. We refer to these as special projects.
Special projects are tightly integrated with your Maestro process and enable advanced capabilities such as decision logic, UI task handling, or cross-project automation. They are configured once at the solution level and can be reused across multiple process models.
Special projects include:
| Project type | Purpose |
|---|---|
| Agentic project | Hosts reusable agent-based workflows that can be triggered from Maestro. These projects define autonomous or semi-autonomous behavior powered by AI agents or planner components. |
| Workflow project | Provides reusable RPA workflows triggered by Service Tasks. |
| App project | Hosts Action Apps used in User Tasks for human-in-the-loop interactions. |
How to add and use special projects
To add a special project to your solution, use Studio Web to create the project type your Maestro process requires and configure it as a dependency.
-
Open your solution in Studio Web.
-
Select Add Project, then choose the appropriate type (Maestro, Rule, Workflow, or App).
-
After creating the project, it becomes available as a dependency within Maestro.
-
When configuring elements in your process (e.g., a Decision task or User Task), you can reference logic or components from these special projects.
Result: The project is added to the solution and becomes available as a dependency when configuring elements in your Maestro process.
Note:Projects in the same solution automatically share access to variables, schema references, and published assets, which improves modularity and reduces duplication.
Example use case
You model an invoice approval process in Maestro. To support this, your solution includes:
- An Agentic Project that handles exception classification using a trained AI agent before escalation.
- A Rule project that determines approval routing based on invoice amount and region.
- An App project that lets managers approve or reject tasks via a custom interface.
- A Workflow project that validates invoice data before submission.
By organizing your solution this way, you enable flexible, reusable process components managed from a single place.
Read about publishing and deploying solutions in the Studio Web user guide.