- Getting Started
- Demo apps
- How To
- Notifications
- Using VB Expressions
- Designing your App
- 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
- 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
Rule: Trigger workflow
Use the Trigger Workflow rule to invoke a specific .xaml file in an attended automation.
The Trigger Workflow rule helps improve data transfer between Apps and attended robots. To leverage the instant communication with the UiPath® Robot, you must use Studio projects that were designed using the Apps-Workflow Communication template available in UiPath® Studio.
If the process is not running, the first instantiation of the Trigger Workflow rule starts the process through Robot JS, opening the communication channel between UiPath® Apps and UiPath® Robot.
Clicking the Workflow file field opens the Resources panel, which displays the available processes and their workflow files.
The panel lists only the .xaml files that were marked as entry points in the UiPath® Studio project.
Select the workflow which you want to execute when the control is operated. Once selected, the following properties become available:
-
Input Override
-
When started
-
When completed
-
Errors
In this section you can set values for the input arguments of the workflow.
Clicking the Input Override field opens the Resources panel, which displays the available input/output arguments of the selected .xaml file.
Select the input arguments, and set their values as the values of the input controls in your app.
The input argument of the workflow has the following syntax:
Processes.<process_name>.<selected_xaml_file>.<input_argument_name>
The value expression of the Apps control has the following syntax:
<Apps_MainPage_name>.<input_control_name>.value
MainPage.text1.Value
.
In this section you can define rules to be executed right after the execution of the workflow starts.
For example: You can show a spinner icon in this section, and then hide the spinner in the When completed section for workflow that take longer to execute.
In this section you can define rules to be executed after the execution of the workflow completes.
For example: For workflows that take longer to execute, you can show a spinner icon in the When started section, and hide it in this section.
To make it easier for you to observe the instant communication between UiPath® Apps and UiPath® Robot, we have prepared a sample project. Proceed with the following steps:
-
Unzip it to a folder on your local device. It should contain:
-
Real Time City Weather Automation
folder - the Studio project -
Real Time City Details.uiapp
file - the Apps project -
Read Me.txt
file - the project description
-
-
In Studio, browse for the sample project and open the
project.json
file. -
Publish the project to your personal workspace in Orchestrator. The corresponding process is automatically created.
-
In Apps, create a new app by importing the Apps project.
-
Replace the referenced process with the one that was automatically created upon publishing the project to your personal workspace.
Note:If you renamed the process when publishing from Studio, replace any binding to match the new name.
-
Preview your app.
-
Search for a city, then select Enter. Notice how the City Details section is instantly updated with information.
-
Click the Get Weather Details and the Get Pollution Details buttons. Notice how the fields are instantly updated with information.
The first computation takes longer because it is the first instantiation of the job. After that, the job keeps running and instantly returns the results. When you close the Apps session, the job terminates.