Get familiar with Mozart Orchestrator
- Última actualización2026/05/06
Get familiar with Mozart Orchestrator
The Mozart Orchestrator combines a process composer for designing detailed workflows with an execution engine that manages real-time process execution, synchronization, and exception handling across agents, automations, and humans—ensuring consistent, transparent delivery at scale.
The Process Composer (Process design) is the central component of the design-time environment, providing all the essential resources and features—Elements and properties, Variables, Triggers, Process editor, and Process editor toolbars —needed to create and design comprehensive end-to-end process automations. Review the following information to understand the available capabilities that can help you accelerate development and create more robust automations.
Elements and properties
-
Task: Task nodes consist of human tasks such as
Form, Approval, and
Document Validation that display information and
gather inputs from user groups, as well as automated tasks such as
Bot and API that integrate
specialized business services, boosting productivity. A process automation
contains the following elements:
- API: API tasks retrieve data for process automation and respond faster than bot automation when invoked in the same process. The API Task is utilized for API-driven cloud automation, often handling data queries and transformations between different systems.
- Bot: Bots created in the Bot editor perform specific tasks based on triggers or conditions, and they are available for selection in Process editor to automate repetitive, rule-based tasks.
- Filter: You can apply a filter to a process automation variable in Process editor. For example, if you have a table as the output of a form, and one of the columns is labeled Approved, which contains Yes or No values, the filter task will be able to retrieve only the rows that have Yes in that column.
- Process: The Process task is used to initiate child processes from the parent process, enabling data transfer between them.
- Approval: Configure an approval task to share requests with decision-makers before the process automation is completed. The need for approvals applies to many business tasks, such as time off or purchasing requests. Developers can use the approval task to automate a process where users can submit and receive approvals while staying notified of progress without breaking from the streamlined workflow.
- Document Validation: Document automation uses the technology of Automation Co-Pilot for Business users to manage the end-to-end document extraction process. Each incoming document creates a new request, which triggers the extraction process. If a document requires manual validation, the Automation Co-Pilot creates a validation task and assigns it to a validation team.
- Form: Users can easily interact with bots through a customizable web interface that allows for direct engagement and invocation of specific functions. The Form task activity is used to assign a task to a user or group. Forms are associated with a Form task to capture data from a form displayed in Automation Co-Pilot and convert it into a process.
- Conditional: Conditionals are used in process automation to manage the flow of a program based on specific conditions, further enhancing efficiency. The rules and conditions that determine when and how bots and forms interact guide the flow of data and actions within the automation. For example, the If/Else pair and Else If, which facilitate internal and conditional branching in process automation.
-
Event: Event activities in your process determine the start, end,
and ability to skip specific steps or direct the flow to certain stages
based on predefined conditions of your business process, ensuring a
productive and efficient process flow. You can use the following events in
your process automation:
- Start: A start node indicates the beginning of a process. It starts with an input variable. Each process can have only one start node, and start nodes cannot be deleted.
- End: This node denotes the end state of a process, which can be functionally classified as Completed, Failed, or Cancelled.
- Go to : This node denotes the transfer/navigation of flow to another task in the process. Routing a flow to a specific task is usually based on some conditions. Go to is also one of the endpoints of a particular flow in the process.
To adjust or modify the properties of a node, click the element you want to edit and then go to the properties panel on the right side of the interface. In this panel, you will find various options and fields. You can change the values according to the element you selected, customizing the node to better meet your needs.
Triggers
Use the Triggers panel to add web triggers to your business processes. The Triggers enable process automations to start immediately when an event occurs in the external applications. This reduces latency in automation execution and eliminates workarounds such as creating task bots to start the processes. The Triggers panel contains all supported web triggers that you can use to start the configured process automations.
The Mozart Orchestrator supports multiple triggers, thereby allowing you to create process automations that depend on matching events in multiple applications. For example, configure web triggers to start a process when a calendar event occurs in Google Calendar (configured using the Google Calendar web trigger) or Microsoft 365 Calendar (configured using the Universal web trigger). Once configured, the web triggers start listening for specific events in the external applications and start the process immediately when the events occur.
The web triggers in a process work in similar way as web triggers in standalone Task Bots or API Tasks. Drag the applicable triggers to the process canvas and configure the source, conditions, and filters. Once configured, you can proceed to configure the rest of the process artefacts. When you execute the process with triggers, the external application sends the trigger response data. You can save this response data in a record variable and use it in any downstream process artefacts.
Process editor
The editor serves as the central workspace for designing the process blueprint.
In the Process editor, you can create end-to-end process automations that seamlessly connect bots and forms. Each process automation includes the logic that triggers these bots and forms, while also managing the flow of data between them. Once you have developed a process automation, you can check it in to deploy it in the public workspace, making it accessible to other users. You can also import, export, run, delete, and check out process automations as needed.
When you create a new process automation or open an existing one, it opens in the new Process editor by default. You can use the new unified editor's enhanced features and capabilities to start creating and designing in the new editor. This new editor provides clear, visually organized node visualizations, allowing you to work efficiently and design using different tasks, bots, APIs, and forms. The improved usability and navigation make it easier for you to access dependencies without extra steps. These enhanced capabilities allow you to design complex, high-level business process modeling.
See Process Editor.
Process editor toolbars
The Process editor toolbar offers quick access to essential controls for process design. It allows you to implement logic conditions, add swimlanes, and manage endpoints with functions such as copy, paste, and cut. Additionally, you can double-click to replace items directly on the editor, enhancing your workflow efficiency.