- Getting Started
- How To
- Using VB Expressions
- Designing your App
- Controls Overview
- Layout and Styling
- Sample App Layouts
- Icon Controls
- User context references
- Public Apps
- Saving Your App
- App Errors & Troubleshooting
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Rule: Submit Action
- Leveraging RPA in your App
- Supported Process Argument Types
- Replacing a Process
- Referencing a Storage Bucket From Orchestrator
- Connecting Apps to an on-premises Orchestrator instance
- Orchestrator Permissions
- Data Flow Between UiPath Apps and Orchestrator
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Application Lifecycle Management (ALM)
- UiPath First-Party Apps
- Basic Troubleshooting Guide
Referencing a Process From Orchestrator
UiPath Apps offers the the ability to connect an app to an automation process. Your app can be used as an interface for providing inputs to the process or as a visual canvas to display outputs to your users.
Once a process has been published to Orchestrator, you can reference that process from an app.
The following example shows you how to add a published process to an app:
- From an existing app in App Studio, expand the dropdown menu at the right of the Add control button.
A list of tenants for the current account is displayed. Select the tenant that hosts the process you need to reference, then click Next.
- The Add process wizard opens, displaying the list of processes in the selected tenant, grouped by folders.
- Select one or more processes. The right-hand panel displays the description, and the input and output arguments of the highlighted
Check the box next to the process you want to use in your app and click Add.Note: Process permissions are managed in Orchestrator. Make sure you have the right permissions for the process you want to add from Orchestrator.
For specific setup instructions, check out Managing Roles in Orchestrator.Important:
By default, App Studio does not recognize the fields of a .NET object used as an input/output argument for your process (for example, a DataTable object).
To allow App Studio to identify these fields:
- Run your process before adding it to your app. Apps checks the job history and automatically detects the schema/fields of the .NET object.
- Manually specify object fields for process input/output. If your process has no job history, then after you add it to your app, you must manually specify its fields.
Be aware that manually added parameters are removed when the process is refreshed.
To update a referenced process whose workflow was changed, follow these steps:
From the Processes section in the tree view, select the process you want to update.
Click on the Refresh process icon.
To bind an input or output argument to a control or rule using the Expression editor, use the following syntax:
To identify the list of input and output arguments of a process, select it from the Processes list on the left-side panel:
The following example shows how to start a process when a Button control is clicked. You can use the events of any control.
In your app, add a Button control.
Select the Button control, go to the Events tab, and click Create rule. The wizard for configuring rules opens.
From the dropdown, select the Start process rule.
Click the What process to start field. The Resources panel opens, displaying the list of available processes.
Select the process you want to start by double-clicking it.
- An Orchestrator account cannot consume more than 100 unique unattended processes across all of the public apps they use during their account lifetime.
- For on-premises Orchestrator instances, the limitation of 100 unique unattended processes applies across all accounts.
- For cloud Orchestrator instances and non-public apps, the limitation does not apply.