8dd283d3-f623-4bfb-8692-7ef565ea7600.jpg

Regional Director

This package includes the below activities that can create password protected Excel and Word document:

1.  Excel Password Protection
2.  Word Password Protection

The activities take as input an already existing document and the passwords, and output the passwords protected document.

Input:

*   DocumentPath(Required)
*   EditPassword
*   Password

Output:

*   DocumentPath(Required)
*   EditPassword
*   Password

The document of Input.DocumentPath will be read with Input.EditPassword and Input.Password, if they are necessary for open and edit Document. Then, content of the document will be saved to Output.DocumentPath, and be added restrictions for editing and opening with Output.EditPassword and Output.Password when they are not empty.

**Tips**: If input document is password protected, the activities also can be used to change or clear document password by empty output document password input.

**Warning**: If output document path is the same as input document path, input document will be overwritten.

  

  

Note: The functionalities are offered to allow robots to interact directly with existing business processes. They are not designed to provide new information security paradigms, but instead a means to allow the robot to interact with the existing security that is being deployed within a business.

An activity pack used to create password protected Excel and Word documents

Add full path and total of activities of each workflow file in a specified folder to a datatable of output argument.

All of the workflow files in current directory and all its subdirectories will be totaled.

Arguments:

1.  in\_FolderPath (String) - specified folder include some workflow files
2.  out\_TotalResult (DataTable) - output datatable include two column of Workflow FilePath and Total of Activities

This workflow is able to get the total of activities from each workflow file

This package includes the activities below:

1.  Image Cropping
2.  Image Zooming

Image Cropping activity can be used to crop an input image with specified Height, Width, X and Y in pixels.

Image Zooming activity includes the four zooming modes below for zoom an input image:

*   Default - Fixed height and width, the aspect ratio of the original image will be maintained with fill specified background color.
*   HeightWidth - Fixed height and width, the aspect ratio of the original image will not be maintained.
*   Height - Fixed height, the aspect ratio of the original image will be maintained.
*   Width - Fixed width, the aspect ratio of the original image will be maintained.

If a option value is empty or unreasonable, it will be adjusted according to input image size.

An activity pack used to crop and zoom images

It will wait until the command is completed even if it takes more time.

This activity runs in the background and will not affect other running command-line process; thus, it can also be used for multithreaded implementation as it can optimize their efficiency.

Arguments:

*   in\_CommandDirectory (String) - current directory of the command line.
*   in\_CommandString (String) - a string of command for running. e.g. "ipconfig".
*   out\_OutputString (String) - output from command line.

This workflow will run a code in the command line and return its output.

The default ReFrameWork includes **InitAllSettings** process and **Config file**.

InitAllSettings can import key and value from "Settings", "Constants" and "Assets" of the sheet in the config file, and all of them are kept in a Dictionary object.

Most of the times, those configs need to be checked one by one before continuing process.

Add in Config File a "Checkings" sheet that has three types of configurable checks and returns message columns.

Develop a new CheckAllSettings process that can be used to check all of the items in config dictionary.

It can be used for future UiPath projects.

CheckAllSettings process can be used after InitAllSettings, and also can be used in ReFrameWork readily.

CheckAllSettings should be inserted after InitAllSettings and all of the process with edit config object.

Import arguments and make it work.

It has three input arguments, the same as InitAllSettings and two output arguments for returning the check result and message if necessary.

Add in config file a "Checkings" sheet that has three types of configurable checks and returns message columns.

*   Key: Check if the dictionary key exist.
*   Type: Type check of value, involves a null check.
*   Match: The regex used to format check of the string value, check with ToString.
*   Message: a string of message for return, optionally use format items for replacing the value of key, type and match.
*   Description: Description of this check item.

For one key there can be set more than one check items, thus returns a different message when a different check item did not pass.

If the latter check item takes effect, the former check item must be set, or else it will be ignored.

This workflow can be used to check all items in the ReFrameWork config valuable

The the Get All Variable Definitions  provides the full path and all the variable definitions of each workflow file in a specified folder to a DataTable. All the workflow files in the current directory and all their subdirectories will be set up as objects.

Arguments:

*   in\_FolderPath (String) - specified folder that includes workflow files
*   out\_VariableDefinitions (DataTable) - the output DataTable includes the following five columns: Workflow FilePath, Variable Name, Variable Type, Variable Scope and Variable Default.

This snippet will get all the variable definitions from each of your workflow files.

This template has the following attributes:

*   It contains an input file where all the target process paths need to be added.
*   Every process must contain a set of unique numbers where the default row is -1.
*   For the output, result numbers are used to designate each process as the full file paths can be very long.
*   The number of tests can be selected using a dialog.
*   The test will be run until all the target processes have been completed.

The output results will include the below information:

*   **StartTime** – the exact time when the target process has been initiated.
*   **EndTime** – the exact time when the target process has been completed.
*   **RunSeconds** – the target process duration measured in seconds.
*   **ProcessNumber** – the number that was given to the process.
*   **ErrorMessage** - if an error occurs while the process runs, the error message will be recorded here.

Performance testing involves many uncertain environmental factors. To ensure the test results are as accurate as possible, the target process will be run in random order.

Even though the same input will be used, the results will be different every time, this is why, when initiated again, the old results will also be retained.

This workflow is a template for performance testing

This template has the following attributes:

*   It contains an input file where all the target process paths need to be added.
*   Every process must contain a set of unique numbers where the default row is -1.
*   For the output, result numbers are used to designate each process as the full file paths can be very long.
*   The number of tests can be selected using a dialog.
*   The test will be run until all the target processes have been completed.

The output results will include the below information:

*   **StartTime** – the exact time when the target process has been initiated.
*   **EndTime** – the exact time when the target process has been completed.
*   **RunSeconds** – the target process duration measured in seconds.
*   **ProcessNumber** – the number that was given to the process.
*   **ErrorMessage** - if an error occurs while the process runs, the error message will be recorded here.

Performance testing involves many uncertain environmental factors. To ensure the test results are as accurate as possible, the target process will be run in random order.

  

Even though the same input will be used, the results will be different every time, this is why, when initiated again, the old results will also be retained.

This workflow is a template utilized for performance testing.

There are three pain points in the retry functionality of the REFramework.

1.  It can not retry when a system exception occurs in init state.
2.  It can not terminate when frequent system exceptions occur.
3.  It just can retry from the beginning of the process.

The above issues are solved in Retry Enhanced REFramework.

1.  It can set the max init retry number in config file to implement init retry. 
2.  It can set the max continuous retry number to implement process termination.
3.  It divides a process into several child processes and retries from a child process when the system exception occurs and can set the no retry or no limit retry child process in the config file.

A framework that enhances the retry functionality based on the REFramework.

In many processes, the start time of manual steps is uncertain. Due to this uncertainty, the results of the operation can vary. While automating such processes we need a way to simulate this uncertainty so that we can test the automation. Using "random delays" is one of the best solutions for this. By invoking this snippet, a delay of a random duration can be introduced in a given time interval.

  

The range of the random delay can be set by two arguments. If the arguments are not be set, the default for minimum seconds is 0, and maximum value of seconds is 60.

A snippet that can be used to delay a process by a random time interval.

About me