Arguments

An argument is a variable intended for data exchange between processes. It differs from a regular variable by having a Direction property, which determines whether the argument can receive and transmit data to the calling process.

Direction has the following values:

• IN — the argument passes data to the subprocess.
• OUT – the argument returns data from the subprocess.
• IN_OUT – the argument both passes data to and returns data from the subprocess.

To call one process (hereafter referred to as a subprocess) from another, drag it from the Project panel into the triangle that indicates the subprocess call location in the scenario.

To connect to the subprocess arguments, press the button. In the window that opens, under the Target column, specify expressions in the selected programming language (C#, Python, or JavaScript) or the names of variables used when interacting with the subprocess. After finishing the edits, close the window.

Editing an Argument

All arguments are listed in the Arguments panel. To open the editing window, double-click the row of the argument whose value you want to modify.

Using Arguments in Orchestrator

By default, arguments can only be edited by opening the project in Studio. The ability to edit from Orchestrator is configured additionally, for each project process. Only arguments with In and InOut directions can be changed in Orchestrator. At the same time, the project process to which the arguments belong can be either a start process or a non-start process.

The general procedure for using project arguments in Orchestrator is as follows:

1. When creating an RPA project process in Studio, set the Use Orchestrator Arguments parameter.

   

2. Create arguments in this process. Make sure that each argument in the process has the correct direction assigned.

3. Upload the RPA project archive to Orchestrator — the arguments will be added automatically along with the project.

4. On the RPA Projects > All RPA Projects page in Orchestrator, the Arguments button becomes available for any project that contains arguments. Clicking this button displays the default values of all project arguments. You can view arguments of any direction present in the project—In, InOut, and Out. However, the values on this page are for viewing only and cannot be edited.

5. To run the project with arguments through Orchestrator, use tasks. The task launch type, manually or automatically, does not matter.

6. To change the values of the project arguments, go to the Orchestrator Jobs page and select the desired job in the table. If the task executes a project with arguments, an Arguments button will become available for it. Otherwise, it will be inactive.

Click the Arguments button on the tasks page and specify a new value for the arguments you want to change. Remember that even if there are arguments of type Out in the project, only arguments with directions In and InOut will be available for editing.

7. To see how the argument values changed from launch to launch, go to the RPA Projects > All RPA Projects > Arguments page (see point 4). On the argument viewing page, check the Launch History checkbox. As a result, you will see all the values of the arguments that were set in Orchestrator before launching the project and received from the robot after completing/during the project execution.

The Main.ltw process is created with the setting disabled by default. In this case, you need to edit it: select the process in the “Project” panel and call the context menu command Edit item. Then check the box and click OK.