c4a7c20d-6ad1-46c6-b0f1-595699a6e412.jpg

The snippet calculates the internet connection speed by live testing it.

To do this it initiates the download of a specified file from the internet and calculates the time it takes to complete the action. It can be used when starting any automation project type that requires a working and stable internet connection.

If no internet connection is detected the snippet will display as output for the internet speed 0 Kb/sec.

This custom activity is helpful for cases when the required robot parameters change frequently and the real-time data is available in the XML file.

  

If the automation involves configurations which may vary on a day to day basis then it would be a bit tedious to change the parameters in Orchestrator frequently. 

Using this activity the required parameters can be fetched at runtime if the config parametrs are available in XML file.

  

For instance for an automation that will move a file from the source to a final destination and the path changes every day, the parameters need to be updated accordingly.

If the path can be obtained from the source application in XML file format, then this file can be read during runtime and the config can be assigned accordingly.

  

This activity can also be used just to check if specific data exists in the XML file or not. If the specified XPath data exists then the output will be TRUE, if the data does not exist then the output will be FALSE.

  

Detailed explanation of parameters and examples of how to use this activity can be found in the attached manual.

Obtain the required data or configuration parameters from an XML file using XPath.

The package contains the following two activities:

1.Encode URL

2.Decoder URL

  

**URL Encoder** will take the input URL as a string and provide encoded URL as output.

  

**URL Decoder** will take the encoded URL as a string and provide the original decoded URL as the output.

This activity will Encode or Decode the URL according to the provided string input

**ExecuteSingleCommand Activity**: This activity opens the command prompt, executes the provided command and returns the console output as a string.

If the input property SingleLineOutput is set to True then only the specific command output will be retrieved, else by default the entire console output will be fetched.

This activity is helpful when only a single command has to be executed and the command output has to be fetched.

  

**OpenCommandPrompt Activity**: This activity opens the command prompt session and provides the CMD process as output. This activity has no input parameters. The output from this activity is used as input for the activities ExecuteCommand, CloseCommand and GetConsoleOutput.

  

**ExecuteCommand Activity**: This activity executes the specified input command on the already opened command prompt process. This activity is useful when multiple commands have to be executed on the same command prompt session.

  

**CloseCommand Activity**: This activity closes the input stream to the specified command prompt process. This activity must be used after the OpenCommandPrompt and ExecuteCommand activities. 

  

**GetConsoleOutput Activity**: This activity is used to get the command prompt console output as a string once the commands are executed and closed using the ExecuteCommand and CloseCommand activities respectively. The activity has the complete console output of the executed commands of the specified command prompt session. 

  

Complete details of how to use these activities can be found in the attached document.

The package contains five Windows command prompt custom activities. These activities can be used to execute CMD commands and also retrieve the command outputs from the command prompt console

This activity performs a recursive search on specified drives/directories or a system-wide search can also be performed.

  

The activity has two inputs and one output : 

*   **Inputs :**

1.  FileName: Provide the file name that has to be searched. Wildcard characters can also be used. Eg: "test.csv", "\*.csv"  
2.  SearchDirectories: Provide the drives or the directories where the file has to be searched as an array. If this field is left blank, the file will be searched in all the directories.  Eg: {"E:\\" , "F:\\New Folder"}  

*   **Output :**

1\. FileLocations: The full path where the file/files are located as an array.

This activity can be used to find the full file path based on the filename

The assets are created in Orchestrator based on the assets present in the Config file. The executable requires the below parameters as inputs:

1.  **tenantname**: Name of the tenant. This value is available in the API access  section of Orchestrator.
2.  **clientid**:  Client ID. This value is available in the API access section of Orchestrator.
3.  **userkey**: User key. This value is available in the API access section of Orchestrator.
4.  **accountlogicalname**: Logical name of the account. This value is available in the API access section of Orchestrator.
5.  **configfilepath**: Absolute file path of the Config file. For details of the Config file format, please reffer to the attached Word document. Only Text, Bool and Integer asset types are currently supported.
6.  **foldername**: Name of the folder in which the assets must be created. Supports both modern and classic folders. In case assets have to be created in a subfolder, the absolute path of the folder has to be provided. Eg: “PROD/HR/Onboarding”

  

The executable can be run from Command Prompt or Powershell.

  

**Note:** _The solution will create the assets with global scope and empty values. The values of the Assets must be updated using the Orchestrator UI._

This solution aims to automate the process of manual Asset creation using Orchestrator UI. Create the Assets in Modern or Classic folders directly based on the Config file used for the project.

The process performs a recursive search on specified drives / directories, or a system-wide search can also be performed.

  

It has two inputs and one output:

*   **Inputs:**

1.  FileName: Provide the file name that has to be searched. Wildcard characters can also be used. E.g.: "test.csv", "\*.csv".
2.  SearchDirectories: Provide the drives or the directories where the file has to be searched as an array. If this field is left blank, the file will be searched in all the directories.  E.g.: {"E:\\" , "F:\\New Folder"}.

*   **Output :**

1\. FileLocations: The full path where the file/files are located is displayed.

This automation can be used to find the full file path based on the filename.

This custom rule can be used to check if there are any spelling errors in the LogMessage activity.

  

The package contains one rule file along with other dependency files.

*   **SpellCheck.Rules.dll**

This rule will examine the string within the LogMessage and check if any spelling errors are present. 

The rule will not check the spelling of the variables used in the LogMessage activity.

  

These small spelling errors generally go unnoticed during manual reviews and make their way to further stages.

Even though these small spell errors may not break the code, making sure that there are no spelling errors within the logs will increase readability and debugging of logs.

  

The rule also provides recommendations for the misspelled words.

  

**Note:** For the complete details regarding the installation steps refer to the attached document.

Custom Workflow Analyzer Rule to check spelling errors in the LogMessage activity.

If you have multiple automation projects that invoke Python scripts, you may eventually run into a situation where you would need to use different versions of the same Python libraries across different projects, but would need to share a common production environment. 

If you have a system-wide installation of Python libraries, this might cause the bots to break in production.

  

Using **venv** you can create lightweight “virtual environments” which provide the ability to have project-specific dependencies installed in a virtual environment, instead of forcing you to install your packages system-wide.

Using this custom activity, you can create a Python venv during runtime from UiPath, and then use this venv to run the Python scripts within the automation.

About me