Bot Bites 2021-08-04T14:40:33+00:00

Bot BitesAutomation Tip Videos

RPA Developers
Business Analysts
Automation Leads

Make Sure Your Applications Have a UAT or Test Environment

Make Automations Configurable for Enhanced Scalability

Best Practices for Preventable Bot Failures

Restart Bot Machines Weekly

Design Loosely Coupled Automation Workflows During Development

Avoid Using Global Variables

Include as Much Error Handling as Possible

How to Identify Process Enhancements Through Monitoring

Couple Bot/Process Test Data with the Runbooks

Using LINQ to Filter a Datatable

Schedule Frequent Code Reviews with Your Team

Check all Available Resources Before Starting Development

Use Descriptive and Consistent Names for Workflows, Variables and Activities

Create Automations as Reusable as Possible Using Variables over Hard-Coded Info

Think ahead during development to write code that can be reused in later projects

Minimize the Number of Attributes Down to a Necessity

Get a Mouse with Extra Buttons to Match to Your Most Used Automation Activities

Always Unit Test Your Code

Flexibility in Solution Design Mitigates Risk for Major Code Changes Later On

Always Make Your Automation as Configurable as Possible

Group Related Activities Together in a Sequence

Provide Multiple Demos As You Go Through Development

Consider ROI Beyond Dollar Savings

Get Creative with Solution Development

Importance of Log Messages in Business Exceptions

Look at the Big Picture When Reviewing a Solution

Perform a Sanity Test Before Moving from Development to Production

Assess Processes Based on Ease of Implementation

Take Time to Learn the Business Applications You’re Working With

Always Annotate Your Modules and Arguments

When Building Attended Automations Avoid a Message Box as the Last Step

Use Module Templates to Organize and Standardize:

When Using StudioX Separate Your Workflow Using Sequences:

Use Two Informative Logs

Always Ask For More Test Data Than You Think You’ll Need

The Importance of Code Reusability

Allocate Ample Time for Automation Testing

Always Name Your Activities in Development

Access Table Data By Column Name

UAT Best Practices

When Assessing Processes for Automation Start with Case Types

Zoom Out to See the Full Context of Your Bot Within Your Business

Embrace the Bugs!

Mitigate Error Solution Delays with Effective Communication and Immediacy

Don’t Undervalue The Automations in Your Organization

Design Your High-Level Maps as “To Be” Instead of “As Is”

Note all Process Changes in the PDD During Development

Identify All Necessary Data Sources Prior to Development

Do a Complete Dry Run of the Process After the Documentation Phase

Look for Areas of Process Improvement During Discovery

The Importance of Standardized SME Interviews

Use a Robotic Portfolio Management Tool to Optimize and Organize Your Automations

Plan Ahead the Individual Sections of a Process

As a Business Analyst There are no Insignificant Questions

When Making a PDD Remember the Basics

Bridge the Gab Between Client and Automation Developer

Ask as Many Questions as You Can in the Beginning

4 Things to Look For When Selecting a Process for Process Mining

Establish Support for Your RPA Program

Treat Bots as New Employees

Have Consistent and Unique Logs Across Your Digital Workforce

Focus on Daily, High-Volume Processes

Take Advantage of the Tools the Language Provides You

Interested in RPA +
Automation updates?

Loading Gif Image Submit