Adding functionalities

You can configure an agentic process model with runtime implementation instructions via the canvas integrated within UiPath^® Studio Web. Studio Web enables you to implement, test, and deploy Maestro models using advanced developer tools that are tailored to your process needs. This unified developer experience allows you to create processes powered by automations, AI agents, human-in-the-loop tasks and system of record connections, which are then executed on a dedicated process engine.

Start by either importing a BPMN model or drawing new one. See for canvas features details.

Properties panel

A business process is primarily implemented by selecting elements and configuring them through the properties panel. You can access the properties panel by selecting the icon in the upper right-hand corner.

The Properties panel has several sections for configurations depending on the element.

General

• Name - the label you see on the canvas
• ID - the system generated unique ID. This is the value used to reference the element in other properties and expressions
• Description - additional details for the element

Implementation

Type specific details for the selected element, such as Start and wait for automation or Start and wait for agent for a Service Task element.

Inputs

Inputs for the selected element may include required fields.

Outputs

Outputs for the selected element. These outputs will be available as variables or expressions in other elements.

Variables and Expression editor

Use the tune selector next to a Properties panel input field to switch between text, variables, and expressions.

• Use variable—select existing variable or element output value
• Open expression editor - build complex expression
• Use JSON editor - use JSON editor to create input
• Use datetime - use date time picker
• Use Data Fabric - use properties from Data Fabric entity

Use Variables to configure element properties and pass values between your elements, automations, agents, app tasks, and connections. Element outputs are automatically available as variables throughout the process.

Use the Expression editor to write more complex expressions to configure element properties. The Expression editor is available for most element properties and features intelligent code completion for variables, arguments, methods, properties, objects, or keywords. You can write expressions on multiple lines and use Ctrl + Space to see the list of available options. Open the Variable selection panel to select a variable, argument, or property. Provide and test values in the Validate expression panel.

Use JSON Editor to construct JSON input.

Note:

Read the DynamicExpresso GitHub documentation for information on authoring expressions.

Tasks

Tasks provide the building blocks for process execution. UiPath platform capabilities are accessed via standard BPMN task types.

Service Task

Used to configure a call to start and wait on execution external to the process engine, typically to another UiPath service, such as automation, agent, or queues.

Workflows

Supports deployed Workflows.

Implementation > Type: Start and wait for RPA workflow.

Agents

Supports deployed Agents.

Implementation > Type: Start and wait for RPA workflow.

Queues

Supports deployed Queues.

Implementation > Type: Create and wait for queue item.

User Task

Used to configure a step in the process execution that requires a human-in-the-loop to perform. This step can contain details for the assignees, task form, inputs, outputs, and escalations. The process execution pauses at this step until an assignee has completed the task.

Supports deployed Action Center Action apps.

Implementation > Type: Create action app task.

See Action Center - Action apps for more details on building and configuring Action apps for Action Center.

Send Task

Used to configure a call to an external system. Process execution makes the call and completes in synchronous nature.

Supports Integration Services connector activities, including custom connectors.

Implementation > Type: Execute connector activity.

Receive Task

Used to configure a trigger from an external system. Process execution pauses and waits for the configured trigger to occur before continuing with execution.

Supports Integration Services connector triggers, including custom connectors.

Implementation > Type: Wait for connector event.

Business Rule Task

Used to configure the execution of a Business Rule (DMN). Process executionmakes the call and completes in synchronous nature.

Supports Business Rules in DMN 1.3 stored in Orchestrator.

Implementation > Type: Execute Business Rule.

Markers

Use markers to configure the execution of a certain task type to create multiple executions by iterating over a List variable.

With any task type selected, select Change element and choose one of the marker types.

Parallel multi-instance

The task executes in parallel and waits for all runs to be completed successfully before continuing to execute the rest of the process.

Sequential multi-instance

The task executes each item in the list one by one, waiting for each to be completed successfully before starting the next one. Once all tasks are completed, the rest of the process continues executing.

Gateways

Gateways provide flow control for your process. You can configure condition logic to determine which path to take. Once the paths are drawn, you can set the condition logic either via the path line or directly on the gateway.

Exclusive gateway

An exclusive gateway is used to configure one or more paths, but only one path is taken based on the conditions.

Inclusive gateway

An inclusive gateway is used to configure multiple paths to be taken simultaneously depending on conditions.

Parallel gateway

A parallel gateway is used to configure a split into multiple paths of execution, or to merge multiple incoming paths of execution. A split creates parallel executions for all outgoing paths.

Event gateway

An event gateway is used to configure a wait for a trigger from one of at least two parallel paths of execution. Execution pauses at the event gateway until one of the paths is triggered. Each path must contain an intermediate catch event, which can be a timer, message, or event.

Events

Events provide the ability to describe when something happens during process execution. There are three main types of events in process diagramming: start, intermediate, and end events. These events are also referred to as either "catching" events, which react to a trigger, or "throwing" events, which create a trigger.

Subprocess

A subprocess is a collection of other tasks and subprocesses that helps to split a complex process into more manageable and navigable parts.

See Process Modeling for additional details on BPMN support timing.