- Getting Started
- Demo apps
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Designing your App with Autopilot
- 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
- Input and Output Type Properties
- Apps and attended automations: bi-directional and instant communication
- 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
- Leveraging Connections in your apps
- Web apps in Studio Web
- Application Lifecycle Management (ALM)
- UiPath® First-Party Apps
- Basic Troubleshooting Guide
Apps and attended automations: bi-directional and instant communication
The bi-directional and instant communication between Apps and attended automations addresses the delayed user experience whenever an attended automation is started from Apps. This solution overcomes the time UiPath® Robot takes to start up every time your apps starts an attended automation by:
-
Decreasing the total execution time.
-
Opening a bi-directional communication channel between Apps and the attended robot.
-
Keeping the communication channel open for instant responses, until the app session is closed.
This way, Apps starts the process only once, then it invokes the .xaml files associated to different user interactions.
To leverage the bi-directional and instant communication between Apps and attended automations, use the following activities and rules:
-
In UiPath® Studio, use:
-
Apps request triggeractivity
-
Handle apps request activity
-
Apps-Workflow communication template
-
-
In Apps, use:
-
Trigger workflow rule
-
To get a sense of how these components work together for an instant communication, see this example.
Use these guidelines when you create your workflow with bi-directional and instant communication:
-
The Send Interim Result activity is not supported by this feature. Avoid adding this activity in the workflows that use the bi-directional communication.
-
In Apps Studio, you need to manually define the properties of complex objects, such as datatables or .net objects. For example, if you are using a data table as an output argument for a process, you must specify the data table column in the process Details page.
-
In UiPath® Studio, mark the .xaml files invoked by your app as entry points. This way, the .xaml files are displayed in Apps Studio when you reference the associated process.
Note:Apps Studio displays all .xaml files which are marked as entry points, regardless they are part of a workflow that uses bi-directional communication or not.
-
The bi-directional communication process has to be started by the app that referenced it.
-
If possible, use the Starts in Background option for these UiPath® Studio projects. This is helpful to have the same app running simultaneously in multiple browser windows, without throwing errors.
