UiPath Orchestrator

The UiPath Orchestrator Guide

Example of Using Input and Output Arguments

To help you get a better understanding of how you could use input and output parameters 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.

  1. Please download the example package. The Studio workflow is also available for download here.
  2. Upload the archive to your Orchestrator instance, using the Upload Package option. At this level, you can see 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 Username and Password arguments and therefore you can see in Orchestrator that the values are inherited from the package.
  1. Deploy the process to an environment.
  2. Open the View Process window. At this level, you can edit the value of the input parameters, be it inherited from Studio or not.
  3. Change the value of the Password argument to 1234567890, for example. The value is displayed as such in the View Process window.
  1. Click Update. The new value for the input parameter is saved.
  2. Open the Start Job window, select the example process, and a Robot of your choosing. In the Parameters tab, you can view that the values were inherited from the package and process.
  3. Edit the values of both input parameters with your credentials and click Start. The job is processed successfully.
  1. Open the Job Details window. Please note that the input parameters' 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 parameter.

Updated 6 days ago

Example of Using Input and Output Arguments

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.