- Getting started
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- Enforcing user-level Integration Service connection governance
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Resource Catalog Service
- Automation Suite Robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Indexes
- Orchestrator testing
- Integrations
- Example of Using Input and Output Arguments
- Troubleshooting
Orchestrator user guide
Example of Using Input and Output Arguments
To help you get a better understanding of how you could use input and output arguments to your benefit, we created a simple example. It enables you to log in to your UiPath® Forum profile, extract the top discussion topics that day, and write them to an Excel workbook.
This workflow uses In arguments instead of variables for typing your username and password. Additionally, the data extracted from the forum page is stored in an Out argument, and then written to an Excel file.
-
Download the example package. The Studio workflow is also available for download here.
-
Upload the archive to your Orchestrator instance, using the Upload Package option. At this level, you can observe that the package accepts input and output values, and you can view their names, as they were given in Studio. We provided dummy values for the
UsernameandPasswordarguments and therefore you can see in Orchestrator that the values are inherited from the package.Figure 1. Arguments for the uploaded package
-
Deploy the process to an environment.
-
Open the View Process window. At this level, you can edit the value of the input arguments, be it inherited from Studio or not.
-
Change the value of the
Passwordargument to1234567890, for example. The value is displayed as such in the View Process window.Figure 2. Parameters tab
-
Select Update. The new value for the input argument is saved.
-
Open the Start Job window, select the example process, and a Robot of your choosing. In the Arguments tab, you can view that the values were inherited from the package and process.
-
Edit the values of both input arguments with your credentials and select Start. The job is processed successfully.
Figure 3. Editing values of input arguments
-
Open the Job Details window. Please note that the input arguments' values are displayed as you filled them in at step 8. Last but not least, the information extracted from the forum page is displayed as the value of our output argument.
Figure 4. Job Details
