Environment

An automation process may require various environment variables and runtime settings. In the "Environment" section, you can define and configure these variables. For example, if an automation process needs to connect to a database, you can specify the relevant database connection information here. These variables can contain customized information necessary for the automation process to function correctly.

Robbot RPA

This zip file is useful when the automation process needs to be reused in another system or environment. By exporting the file, you can gather all the necessary settings and configurations for the automation process and easily transfer them. For example, after developing an automation process, you can create a zip file containing all the environment settings using the Exported zip file feature. When you want to use it in another system or environment, you can import the zip file and reuse the same settings. This way, you can easily transport the automation process and ensure it works seamlessly in different environments.

UiPath

"Read UiPath execution logs": This field is used to read the log files generated during the execution of the UiPath automation process. This feature is essential for monitoring the execution of the automation process, debugging, and analyzing performance.

"Project files": This field contains the UiPath project files associated with the automation process. These files store the UiPath projects or components required for the automation process to run. This field allows you to identify and manage project files.

"UiRobot.exe path (Optional)": This field specifies the path to the UiPath Robot application's exe file. This file is used in the execution of the UiPath automation process. If the relevant UiPath Robot application exists, you may need to provide the path to the relevant exe file in this field.

"File name (XAML, JSON, or NUPKG) (Optional)": This field specifies the file name for the UiPath automation process. This file may contain the main file or component of the automation process. XAML, JSON, or NUPKG file formats can be used. This field is used to specify the required file name for the automation process.

Automation Anywhere

"ATMX file name to run": This field specifies the name of the ATMX file (Automation Anywhere's workflow file) that needs to be executed. For example, you can specify it as demo.atmx. This file contains the automation workflow that will be run by Automation Anywhere. "Automation Anywhere project files": This field refers to the project files associated with the Automation Anywhere automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the Automation Anywhere script.

WinAutomation

Process Path: This field indicates the path required to run the WinAutomation process. You can write the path in double quotes. For example, /Demo Projects/Sample. This path indicates the location of the WinAutomation process file that will be executed.

Exported process file: This refers to the exported process file of WinAutomation. This file contains all the settings, configurations, and dependencies required for the automation process. The file is created by exporting a WinAutomation process and can be imported and executed in the Robbot Center application.

WinAutomationController.exe path (Optional): This field specifies the path to the WinAutomation Controller executable file. If necessary, you can provide the path to the WinAutomationController.exe file. This file is used to run the WinAutomation process.

WinAutomation.UserAgent.exe path (Optional): This field specifies the path to the WinAutomation User Agent executable file. If necessary, you can provide the path to the WinAutomation.UserAgent.exe file. This file is used to communicate with and interact with the WinAutomation process.

AutoIt

"AU3 file name to run": This field specifies the name of the AutoIt script file (.au3) that needs to be executed. For example, you can specify it as demo.au3. This file contains the AutoIt script that will be run by AutoIt. "AutoIt project files": This field refers to the project files associated with the AutoIt automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the AutoIt script. "AutoIt.exe path (Optional)": This field specifies the path of the AutoIt executable file. If required, you can provide the path of the AutoIt.exe file. This file is used to run the AutoIt script.

TagUI

"TagUI command": This field specifies the TagUI command to be executed. For example, you can use the syntax "tagui main.tagui -s -h" to run the main.tagui script with options for silent mode (-s) and headless mode (-h). This command triggers the execution of the TagUI automation script. "Project files": This field refers to the project files associated with the TagUI automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the TagUI script.

Automagica

"Python alias": This field specifies the Python alias or command to be used when executing the Automagica script. It could be "python" or "python3" depending on your Python installation and configuration. "Script name to run": This field specifies the name of the Automagica script file to be executed. For example, you can specify it as index.js. This file contains the Automagica script that will be run using the specified Python alias. "Pip install before running": This field indicates whether any additional Python packages or dependencies need to be installed before running the Automagica script. It ensures that all the required packages are installed in the environment before executing the script. "Automagica project files": This field refers to the project files associated with the Automagica automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the Automagica script.

Taskt

".xml file name to run": This field specifies the name of the Taskt script file (.xml) that needs to be executed. For example, you can specify it as demo.xml. This file contains the Taskt script that will be run by Taskt. "Taskt.exe path": This field specifies the path of the Taskt executable file. It should provide the location of the Taskt.exe file, which is used to run the Taskt script. "Taskt project files": This field refers to the project files associated with the Taskt automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the Taskt script.

Selenium

"selenium-side-runner your-project.side": This field specifies the command to run the Selenium project using the Selenium-Side Runner. You can replace "your-project.side" with the actual name of your Selenium project file. The Selenium-Side Runner is used to execute Selenium scripts written in the Selenium IDE. "Selenium project files": This field refers to the project files associated with the Selenium automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the Selenium script.

Robot Framework

Framework test using the Robot Framework framework. For example, you can use the syntax "robot demo.robot" to run the test script named demo.robot. This command triggers the execution of the Robot Framework test. "Project files": This field refers to the project files associated with the Robot Framework automation. These files include the necessary resources, configurations, and dependencies required for the automation to run smoothly. It allows you to define and manage the project files associated with the Robot Framework script.

Sikulix

SikuliX is an automation tool used for visual recognition and automation tasks. .sikuli or .skl files are files that contain scripts for SikuliX projects. These files include SikuliX commands used to identify screen images and automate various tasks. .jar files, on the other hand, are executable files of SikuliX. This file can contain a complete version of SikuliX or project files. If you want to use a .sikuli or .skl file, you need to specify the file name or file path. For example, "C:\Users\Username\ProjectFile.sikuli" or simply "ProjectFile.sikuli". If you want to use a .jar file, you need to specify the full file path of SikuliX.jar. For example, C:\SikuliX\SikuliX.jar.

Python

Python Alias: In this section, you need to specify the location or alias of the Python executable file. For example, if the Python executable file is in the system's PATH, you can simply specify "python". If the full file path of the Python file is required, you should provide the complete path. For example, C:\Python\python.exe. Script Name to Run: In this section, you need to specify the name of the Python script you want to run. For example, "main.py". Pip Install Before Running: In this section, you can specify the Python packages that need to be installed before running. These packages can be external dependencies required for your script to work. For example, "requests" or "numpy". Robbot Center will use the pip command to install these packages before execution. Project Files: In this section, you can specify other files that are required for your script to run. For example, data files used by your script, configuration files, etc.

Docker

Image Name of the Docker Image: In this section, you need to specify the name of the Docker image you want to use. A Docker image is a preconfigured package that contains the environment and components required for an application to run. For example, my-docker-image. Filename of the Docker Image: In this section, you need to specify the file name of the Docker image. This refers to the file name of the Docker image on disk. For example, "docker-image.tar.gz". Port Mapping: In this section, you can specify which ports the Docker image will use to provide services. For example, if you want to map port 8080 on your local machine to port 80 in your Docker image, you can specify "8080:80" for port mapping. Zipped Docker Image: In this section, you can specify a compressed zip file of the Docker image. This is a compressed format for sharing or transporting your Docker image. For example, "docker-image.zip".

Node Js

Script Name to Run: In this section, you need to specify the name of the Node.js script you want to run. For example, index.js. npm Install Before Running: In this section, you can specify the Node.js packages that need to be installed before running. These packages can be external dependencies required for your script to work. For example, "express" or "axios". Robbot Center will use the npm command to install these packages before execution. Project Files: In this section, you can specify other files that are required for your script to run. For example, data files used by your script, configuration files, etc.

Dotnet

Executable File Name: In this section, you need to specify the name of the executable file of your .NET application that you want to run. For example, HelloWorld.exe. Project Files: In this section, you can specify other files that are required for your application to run. These files can include the source files of your .NET project, configuration files, data files, and so on.

PHP

Script Name to Run: In this section, you need to specify the name of the PHP script you want to run. For example, index.php. Composer Install Before Running: In this section, you can specify the PHP packages that need to be installed before running. These packages can be external dependencies required for your script to work. For example, "guzzlehttp/guzzle" or "symfony/console". Robbot Center will use the Composer command to install these packages before execution. Project Files: In this section, you can specify other files that are required for your script to run. For example, data files used by your script, configuration files, etc.

AD Sync

"Active Directory Fields" include the fields used to configure Active Directory (AD) integration in the Robbot Center application. These fields contain the necessary information to establish a connection between the AD environment and the Robbot Center application and to perform operations related to user accounts.

Robbot Auth URL: In this field, you need to enter the URL of the Robbot authentication service. The URL should indicate the location where Robbot's authentication API can be accessed. For example: "https://gateway.domain.com/api".

Robbot Auth Client ID: In this field, you should provide the client ID associated with the Robbot authentication service. The client ID is a unique identifier assigned to Robbot Center by the Robbot service, and it helps establish a trusted connection between Robbot Center and Robbot for authentication purposes.

Robbot Auth Client Secret: This field requires entering the client secret associated with the Robbot authentication service. The client secret is a confidential key used to authenticate the Robbot Center application with Robbot. It should be treated as sensitive information and kept securely.

AD Password Reset

Key: Robbot Auth URL

• Value: The URL of the Robbot authentication service. For example: https://gateway.domain.com/api

Key: Robbot Auth Client ID

• Value: The client ID associated with the Robbot authentication service. For example: ABC123DEF456

Key: Robbot Auth Client Secret

• Value: The client secret associated with the Robbot authentication service. For example: ************

AD Unlock

AD Unlock Fields:

Key: Robbot Auth URL

Value: The URL of the Robbot authentication service. For example: https://gateway.domain.com/api

Key: Robbot Auth Client ID

Value: The client ID associated with the Robbot authentication service. For example: ABC123DEF456

Key: Robbot Auth Client Secret

Value: The client secret associated with the Robbot authentication service. For example: ************

AD Enable/Disable

AD Enable/Disable Fields:

Key: Robbot Auth URL

Value: The URL of the Robbot authentication service. For example: https://gateway.domain.com/api

Key: Robbot Auth Client ID

Value: The client ID associated with the Robbot authentication service. For example: ABC123DEF456

Key: Robbot Auth Client Secret

Value: The client secret associated with the Robbot authentication service. For example: ************

Type: This field indicates the action type selected by the user. The action type can be one of the following: "enable" (to enable), "disable" (to disable), or "disable and remove groups" (to disable and remove groups). These types specify different operations for enabling or disabling AD user accounts and removing group memberships.

AD Add Member

AD Add Member Fields:

Key: Robbot Auth URL

Value: The URL of the Robbot authentication service. For example: https://gateway.domain.com/api

Key: Robbot Auth Client ID

Value: The client ID associated with the Robbot authentication service. For example: ABC123DEF456

Key: Robbot Auth Client Secret

Value: The client secret associated with the Robbot authentication service. For example: ************

Outlook

Outlook Fields:

Key: Robbot Auth URL

Value: The URL of the Robbot authentication service. For example: https://gateway.domain.com/api

Key: Robbot Auth Client ID

Value: The client ID associated with the Robbot authentication service. For example: ABC123DEF456

Key: Robbot Auth Client Secret

Value: The client secret associated with the Robbot authentication service. For example: ************

Custom

Custom Fields:

Key: Robbot Auth URL

Value: The URL of the Robbot authentication service. For example: https://gateway.domain.com/api

Key: Robbot Auth Client ID

Value: The client ID associated with the Robbot authentication service. For example: ABC123DEF456

Key: Robbot Auth Client Secret

Value: The client secret associated with the Robbot authentication service. For example: ************