RPA – UiPath-Best Practices Guidelines

RPA UiPath Best Practices Guidelines

RPA is a form of business process automation that allows anyone to define a set of instructions for a robot to perform a defined task. UiPath is a RPA tool used for Web automation, PDF automation, Windows desktop automation etc. This tool can be used for redundant tasks.

UiPath tool allows user to draw a workflow within a flow chart editor. This is helpful and hence, it is marketed as “No Coding” solution.

Many companies have started using RPA due to increase in demand.

While we talk and discuss about RPA/UiPath, here are some best practices we should not forget to follow.

There are some key benefits which we get by following the best practices while development: –

Best development practices

We, as developers, should follow a common framework within the organization. It is a responsibility of a solution architect to build and maintain a standard best practices guideline for developers/for an organization. However, we should know the basic and standard best practices for developing automation workflows.

Mentioned below are some of the quite common practices that we can introduce into our workflows:

Variable Naming Convention

Variable should follow the camel Case naming convention and cannot be single word. Also, Variable cannot start with the “var” prefix

        Good Example Bad Example

Examples

Argument Naming Convention:

Argument should follow the Title Case naming convention and cannot be a single word. All argument should start with the “in”,”out”,”io” prefix, which need to be written in lower case.

Argument Naming Convention examples

Empty Catch Block:

Catch block of Try Catch activities should never be in empty state. At least a Log Message activity should be added into the Catch Block.

Empty catch block examples

Empty Workflow:

There should not be empty workflow files, including sequences,flowcharts, state machine.

Empty workflow

Large Idx in selectors:

Shows the selectors that contain an “idx” attribute greater than 2. This attribute is used to distinguish elements with the same selector based on their order in the interface hierarchy. This order can change if the elements you are automating change, so this attribute should be avoided to avoid the selection of wrong elements.

Consider using other attributes in the selector to make it less dependent on the “idx” attribute. Also, reducing indexes can be achieved by adding information about ancestor elements, using relative elements or the “Anchor Base” activity.

Large Idx in selectors

Unreachable Activities:

It is not recommended to have not connected nodes in flowchart or activities that commented out or that not connected to any node in a flow chart. All these kinds of activities should be removed before publishing to the orchestrator.

Unreachable activities

Nested IF Activities:

It is recommended to have 3 or less 3 nested if clauses in file or project. In such conditions always try to use Switch Activity or Flowcharts.

Nested IF Activities

Empty Sequence:

There should be any empty sequences in between the workflow.

Bad example

Unused Variable:

Most of the time while development we create variable just of the testing purpose and at the end of the development, we forget to remove those variables. It always recommended to remove all the unused variable from all the workflows files. To achieve that you can use the below option from the UIPATH Studio.

Unused Variable

Unused Dependencies:

Always remove the packages from the projects which is not being used before published to the orchestrator.

Unused Dependencies

Simulate Click Check:

Whenever any of the activity which has “Simulate Click” property it should be checked. Using “Simulate Click” doesn’t rely on the mouse driver, so it provides a faster way of performing click actions.

Simulate Click Check

Simulate Type Check:

Whenever any of the activity which has “Simulate Type” property it should be checked. Using “Simulate Type” doesn’t rely on the keyboard driver, so it provides a faster way of performing type actions.

Simulate Type Check

Open Application Wrongly User:

It is always recommended to use open browser activity to open any web portal, please don’t user open application scope for browser activities.

Open Application Wrongly User

Container Usage:

Always checks if consecutive activities in your automation are using the same top-level- selector instead of using a container with a single selector. We recommend as a best practice to use scope, such as ‘Open Browser” or “Open Application”. when performing multiple action on the same UI element, as this method is more reliable instead of targeting each activity on the same selector.

Container Usage

ContinueOnErrorTrue:

All the activities which contain ContinieOnError option in property is always uncheck. When this property is set to True, all error that occur during the execution of the activity are ignored, which is why this option should be uncheck.

ContinueOnErrorTrue

Kill Process Activity not allowed:

For killing any of process it is always recommended to use the “Kill Process for Current User” instead of “Kill Process” Activity.

Kill Process Activitynot allowed

Repeated Display Name in Activities:

All the activities in the workflow should have unique name so that they can be easily identifies/modified if required. This is also help while debugging the code. If you face any error in production so can directly check the activity name and directly go the process rectify the error.

Repeated Display Name in Activities

Hotkey Without Selectors:

All the “Send “Hotkey” activity should be inside any container like “Attached Window/Browser” or “Open Application Browser” or should have selector in it.

Hotkey Without Selectors

WaitForReady not set as complete:

Whenever you are using any activity which contains waitforready property it should always be in values as “COMPLETE”.

WaitForReady not set as complete

Empty Else Block:

Whenever you are using “IF” activity always recommended to use at least log message in the else block, please do not leave else block empty.

Empty Else Block

Password printing log Activity:

Always keep your all the password in assets and always use secure string data type for passwords and never ever print your password in log activity.

Password printing log Activity

WildCard and UnderScore not allowed in ‘parentclass’,’class’,’id’ and ‘parentid’:

Always recommended not use wildcards and underscore in ‘parentclass’,’class’,’id’ and ‘parentid’ attributes.

Hard coded digits not allowed in the ‘tablerow’ attributes:

Always recommended to use variables or dynamic values instead of the hard-coded number.

Xaml filename contains spaces:

Always recommended to not use any kind of spaces into the xaml file name.

Xaml filename contains spaces

Leave a Reply

Retype the CAPTCHA code from the image
Change the CAPTCHA codeSpeak the CAPTCHA code
 

SOAIS - Worksoft Newsletter

To view on your browser, click here
Facebook Twitter LinkedIn
Dear Default Value,
 

Welcome to SOAIS Newsletter of September 2021!

Continuous Testing with Remote Execution
 
The speed of innovation continues to increase, driving rapid and relentless change for today’s ever-evolving IT landscapes, creating greater risk as IT and business teams scramble to ensure timely delivery. How can your organization keep pace? Test more, worry less. With Worksoft’s Connective Automation Platform, you can easily build and maintain automated tests, accelerating testing time without losing scope or volume. You can schedule and execute remote, continuous tests to intercept defects sooner and prioritize remediation - without sacrificing your nights and weekends. Explore how continuous test automation and remote execution can empower your organization.

Click here to connect with us to get more information on our services.
 

Skip Costly Rework with Dynamic Change Resiliency​

Change resiliency is imperative in ever-evolving IT environments. Our patented object action framework streamlines change management by assigning object definitions to your shared assets. The same object may be used in a thousand automation steps, but it can be easily updated by making one simple change to the model definition. The change automatically propagates to every single instance where that object may have been used without a single line of code or manual human involvement. For more change readiness you can also engage our Impact Analysis for SAP to predict how changes in SAP transports will affect your business processes. 

Please click here to watch the video to get a gist.
 

SOAIS Blog – Nuts and bolts of Certify Database Maintenance​

One of the key thing, which is often missed by the organizations, who have invested in using Worksoft Certify for automating their Business Process Validation initiatives, is implementing a Database Maintenance Plan. While the business and the test automation consultants get excited about the shiny new thing that they have got and start building the regression suite; planning and executing a database maintenance plan for most of the customers gets pushed down the priority list. However, since all the test assets in Certify are stored in a Database, a robust database maintenance plan is very important to maintain smooth operation of Certify with acceptable performance criteria. The customers usually start facing issues once they have built significant number of Certify processes which they have started executing on regular basis. Such executions add a lot of data to the tables storing results data and increase the overall size of the Certify database.

Please click here to read the complete blog.
 

Worksoft Blog – Process Intelligence: A Multi-Dimensional Approach

The ability to extract process knowledge has become easier through the years. Technology has evolved to the point where we can deploy capabilities that connect at multiple levels to extract different types of process insight. In the past, organizations were forced to spend enormous energy extracting data manually from different applications and databases. Then, they would have to use things like spreadsheets to transform the data and convert it into meaningful information. 

Please click here and read the complete blog.
 
India
Unit 9, Level 5, Navigator, ITPL,
Bangalore - 560 066.
Phone: +91 80 40071234
US
Suite 101, 1979, N Mill St,
Naperville, IL 60563
Phone 1-800-262-2427
Please click here to Unsubscribe / Unsubscribe Preferences

Leave us your info