Skip to main content

Pathfinder Blog

Explore community shared insights & innovations.

  • 318 Topics
  • 248 Replies
318 Topics
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Building Secure and Auditable Bots in Automation 360

As Robotic Process Automation activities expand within businesses, not all bot developers are well versed in best practices for developing secure and auditable bots. While enabling federated development to many business groups within the organization has its benefits – namely increased productivity and speed of execution for redundant processes – it can come at the potential risk for data loss and an overall decrease in the confidentiality of business data. Many businesses attempt to overcome these challenges through the use of a Center of Excellence (CoE) that reviews bots and may run code scanning analyzers in an attempt to increase adherence to corporate and IT standards. This helps to minimize the risk. However, more can and should be done in the design of a bot to help ensure businesses can continue to receive the value from RPA while mitigating as many risks as possible. The following are some additional guidelines that can be followed to mitigate risks: Don’t use external files

1340
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Intro to Conditional Statements

In this post, we'll look at one of the three tenets of problem-solving: Selection. Selection is the process of taking action (or not) based on the evaluation of a condition(s). If the condition resolves to true, the corresponding actions are taken. If the condition does not resolve to true, then alternate actions (or no actions at all) may be taken. There are plenty of examples in our day to day business operations where conditional statements come into play...likely without us really naming them as such. As you read through each statement below, think about what action takes place when the condition is true vs the action (if any) that takes place if the condition is not true. Additionally, see if you can identify what part of the statement is the condition vs the corresponding action. Examples: If there is a new invoice on the X drive (a shared folder), then Nacy will pay it. The condition in this example is "a new invoice on the X drive" If a new invoice shows up, then Nacy will pay

2130
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Intelligent Automation Pt II: Building the Bot

Intelligent automation is the sweet spot between robotic process automation (RPA) and the broad categorization of artificial intelligence (AI) to mimic cognitive decision making in task automation. In this second part of our 2 part series on intelligent automation, we'll be using the Machine Learning Classifier tool discuss in part one to assist in training a machine learning model, and using that model from within our bot to appropriately classify IT helpdesk tickets. Note: if you haven't checked out part I of our series, check that out here to get a background on the use case introduced as well as the tool we'll be using in this session. If you want to follow along in the AAillustrates session, you'll need the following resources: An Enterprise/Community A2019 Account You can use Automation Anywhere Enterprise A2019 or Automation Anywhere Community Edition. If you don't yet have an account, be sure to sign up here so you can get started in setting up your environment and getting your

1460
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
V11 Bot Submission Checklist

1. Vendor Registration (required for first submissions only) Every developer/organization that posts bots on Bot Store is required to register. This registration is handled by the vendor registration process. Here, developers/organizations will need to enter some basic details about themselves/their organization as well as a logo/emblem that can be used on their bots. This is only a one-time process to be set up as a vendor. Bots submitted after this initial vendor registration process can all be linked to the existing registered vendor. This is a great way for individual developers to create an online reputation for themselves as being expert bot builders. This is also a great way for organizations and service providers to showcase some of their work and possibly build a pipeline for future engagements. For the creation of a paid bot or DigitalWorker, you'll also need to request for a Global ID. This Global ID is used for your bot's licensing to enforce timing for 30-day free trials a

1630
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Automation 360 Bot Submission Checklist

Automation 360 Bot Store Submission Checklist 1. Vendor Registration (required for first submissions only) Every developer/organization that posts bots on Bot Store are required to register. After you submit your first automation, we’ll reach out to ask for your organization details and work with you to set up your Bot Store profile. This is a great way for individual developers to create an online reputation for themselves as being expert bot builders. This is also a great way for organizations and service providers to showcase some of their work and possibly build a pipeline for future engagements. 2. Read Me File Content and FormatRead Me files are critical and required for submitting a bot or package successfully. The Read Me file template contains the necessary details that a customer would need to get started with a bot or package. Most importantly - think about your audience when creating your Read Me. Not all Automation Anywhere developers come from traditional development back

4900
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Enterprise A2019 Release Highlights: A2019.16

In this update, learn about the newest updates to the Automation Anywhere Enterprise A2019 platform including: AARI - the Automation Anywhere Robotic Interface Discovery Bot - the process discovery tool that helps organizations identify automation opportunities, and begin building automations based on recorded processes. IQ Bot - updates to IQ Bot's ability to extract text - now with image preprocessing capabilities and Python integration Enterprise A2019 Updates - multi-user support for terminal server connections and new deployment options for the bot agent client Bot Insight - updates to the analytics capabilities of Bot Insight allow for tracking of attended automation tasks

170
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Automation 360 Tutorial: Car Images background updating Bot

In this tutorial, we will build a bot to change the background for multiple car images. Here is the use case we are addressing: A car dealer has pictures of his car inventory with non-uniform backgrounds. He wants to remove the background for each picture and update it to have a uniform branded background. Let's see how we can build a bot in Automation 360 to update all the images. This bot can be used to update/remove background images for other use cases such as: Updating employee profile pictures Media houses use images without a background in different editorial sections Marketing teams use it to update image backgrounds to suit different ads based on the context Here is the data setup required to build this bot: Download the folders with different car images here. Here are the pictures for your reference: Download the background template image here. Let's start building the bot by following the steps as shared below: Log in to the Automation 360 Control Room. Go to Bots - My bots,

1920
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
QuickTip: Using the JSON Object Manager Package

In this session, we'll look at how to use the JSON Object Manager package available for download from Bot Store. This package can be used for retrieving data from the JSON response of a REST web service call, reading JSON config files, getting the length of an array object within a JSON, or for updating JSON values based on the value's key. Note: If you are using Automation Anywhere A2019 Community Edition, this package has already been installed for you. Reference Link: Please find the link to the JSON used in the video here. As is done in the video, you can use a REST Get action and use the provided GitHub URL to fetch the JSON. Video Recap Initialize the Session Using the package starts with initializing a session. This means using the initialize action in conjunction with the full JSON (either from the response body of a REST call or after read from a JSON file itself) The initialize action validates that the JSON is valid, and will set you up for being able to query the JSON's val

18870
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Automation 360 Tutorial: Working with Office 365 One Drive Package

In this tutorial, we will look at how to use Office 365 One Drive Package in Automation 360 platform. Pre-requisites: Active Office 365 subscription Office 365 Username Office 365 Password Office 365 Tenant Id Office 365 Client Id Office 365 Client Secret First lets set up the App and credentials in Azure (https://portal.azure.com/) Login to your Azure Portal Click ‘Azure Active Directory’ (if you don't see it on the home screen, search for Azure Active Directory in the search bar) Note the Tenant Id by clicking the Copy icon shown below. Then click on App Registrations Click ‘New Registrations’. Enter a name ‘Office_365_Permission, select ‘Accounts in any organizational directory (Any Azure AD directory - Multitenant)’ and Click 'Register’. Note down the Application id (i.e.,Client id) and then Click 'Certificates & Secrets'. Click ‘New Client Secret’, Enter the description, Click ‘Add’. Note the Client secret as it will not be visible later on. Once you have noted down the Client sec

21490
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Automation 360 Tutorial: How to use Camunda DMN package from Bot Store

In this tutorial, we will learn about how to use Camunda DMN package available in Bot Store. First let's look at what DMN means and its background. As defined by OMG, DMN (Decision Model and Notation) is a modeling language and notation for the precise specification of business decisions and business rules. DMN is easily readable by the different types of people involved in decision management. These include: business people who specify the rules and monitor their application; business analysts. As referenced in Camunda website, DMN is not owned by a certain enterprise but by an institution (OMG), which is already established through other world-wide standards, e.g., BPMN and UML. The DMN standard is supported by several software products; you are less dependent on any particular vendor’s products. In DMN, decisions can be modeled and executed using the same language. Business analysts can model the rules that lead to a decision in easy to read tables, and those tables can be executed

1110
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Learning to Use the Error Handler Package

Goal number one for any automation being built is obviously to complete the task at hand - be it reconciling data between applications, sending off emails, doing web scraping, and/or some combination of all of the above. That’s why we’re using RPA in the first place right? If your goals stop there though, you may be putting your automation process, bot runner, and possibly other scheduled processes at risk. A clearly defined, and crucially important, goal number two must also be considered: keeping the bot from hard failing. Fortunately approaching this stability focused goal is easy to implement in Enterprise A2019 and should be fearlessly approached by both new and experienced bot builders. In this article, we’ll break down the actions of the Error Handling package to understand the appropriate use for each so your bots can safely exit (and log) should an error occur. Why Error Handling Matters You may have heard of a phrase “happy path” in business process breakdowns or development

5450
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
QuickTip: Advanced Error Handling

In this session, we’ll look at some advanced error handling techniques that can help keep your bots up and running even when dependent applications misbehave. Video Recap Global Debug/Log Flag Most bots that developers create ultimately end up running "headless" on a virtual machine. ("headless" meaning no one is sitting there watching them once in production). Unfortunately that means that when an error occurs, it's not always easy to know exactly what happened, what the machine state was like, or what was actually on screen. One helpful approach around that is to build your bot in a way that its looking for a global value to indicate its log/debug level. In this case, the bot can be set up to do more or less logging dependent on that global log level. This additional logging may include writing out info messages to an audit log (as opposed to only errors) and may also include capturing/saving additional screenshots of the bot execution. Retries Left Loop Concept When working with an

5100
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
QuickTip: Building with Embedded Python

In this session, we'll look at how to embed custom Python in a bot to enhance our ability to quickly and easily extract data. Video Recap: Determine an Order of Operations When mentally thinking through how to solve problems, determine an order of operations for how you'll proceed. As a good practice: Try to solve problems using packages alone. Most of the time this can get you the data/solution you need. When packages leave you short, understand your options...you could use embedded Python, embedded JavaScript, embedded VBScript, write a DLL and use the DLL package, or consider writing your own package (Java). Python Script: Open Action Adding embedded Python to a bot starts with adding the Open Script action. Using this action, developers can choose to execute Python scripts located in their Control Room, on a desktop/share location, a location referenced by a variable, or by manually inputting the script directly into the Open Script action. In the example, we used the manual input

2830
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Control Room OverviewLearning Journey

Objective: Following a tutorial to build a bot is one thing - but it's important as a new bot developer to understand the Control Room, how the development interface is laid out, and the flow that bots typically follow from ideation to public check-in and deployment. The Control Room is the central interface for all things bot management, global value creation, user management, deployment, and testing. All that said, depending on your role within the organization - you may or may not see all of those capabilities from the Automation 360 Control Room interface. While most of your time as a bot builder will be spent in the Bot Editor interface, it's important to recognize what else can be done from the Control Room itself. Take a look at the tabs you most likely have access to as a developer (again, if you don't see all of these tabs in your interface, it’s ok - that’s controlled through your role…it’s most important just to understand what’s possible from this interface at this point):

21660
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Bot Editor Deep DiveLearning Journey

Objective: As you come to understand the capabilities of robotic process automation and using bots to automate redundant, rule-based tasks, it’s important to also understand the capabilities available out-of-box to bot developers. In this learning experience, we’ll highlight the interface and some of the capabilities of the Bot Editor and establish a pattern for learning about how to better understand the use of the available packages. To progress in the use of any application requires an understanding of its capabilities as well as information related to their appropriate application. For bot building, that means diving head first into the capabilities of the Bot Editor. Through the Bot Editor, developers can create, test, and review bot builds. As a bot builder, it’s important you’re familiar with the Bot Editor interface so that you know what packages are available and a general idea of the actions they contain, how to create and modify variables, and how to test (and debug) your bo

960
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Where to Get HelpLearning Journey

Overview: Learning a new skill is challenging - especially when you’re learning on your own - and especially when you’re stuck on something. Thankfully, Automation Anywhere provides some excellent resources to help you get unstuck when you find yourself unsure how to solve a particular problem or deal with an issue you’re seeing. In this learning experience, we’ll break down some of the best available resources to get all your issues straightened out. When learning a new technical skill, there’s this challenging jump that learners must make: leaping from the comfort of doing well laid out tutorials with explicit instruction, to starting to solve problems where the steps to get to that final solution aren't so clear. Welcome to the life of being a problem solver! All joking aside, it can be intimidating when you get stuck on something, especially when you don't feel like you know where to turn to get the problem straightened out. Let’s take a look at some resources made available by Aut

960
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
What Can Bots Actually Do?Learning Journey

Objective: With a foundation of what RPA actually is, it’s important to start thinking about how RPA can be applied. In this learning experience, we’ll take a look at what bots can do and how they can be utilized in different areas of an organization. Bots are RPA: specialized software robots that automate high-volume, repetitive, rule-based tasks in an auditable and reliable way…but what do bots actually do? And how can that help save my organization time, money, reduction in errors, etc? The answer to both of these questions really depends on the manual efforts that take place in different areas within your organization. Take, for example, processing sales orders. Regardless of the size of your organization, there is some place that your company is tracking customer relationship data (in a CRM, xls, some other system of record) where data needs to be updated in the case of a sale. Additionally, most organizations also leverage an enterprise resource planning application as part of th

1400
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Exploring Capabilities in Bot Store

Overview: Identifying some of the most valuable automation opportunities in an organization requires critical thinking and a creative mindset. Those skills come from experience, as well as an exploration in the ‘Art of the Possible’. In this learning experience, we’ll take a look at how Bot Store can be used to explore pre-built bots and packages to enable developers to accelerate bot builds and branch out on bot capabilities. As new developers start to find their groove in developing RPA bots, a trap that many developers fall into is thinking that the automations they build in the future have to be similar to the automations they’ve built in the past. Said another way - it’s important that as you’re learning to build bots, you continue to think “outside the box” as far creatively approaching solutions to automation opportunities. One way to encourage such creative thought is to regularly explore the bots and pre-built packages available in Automation Anywhere’s Bot Store. Bot Store is

590
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Getting Started - Citizen developer JourneyLearning Journey

Overview Welcome to the start of building great intelligent automation! This journey is focused on helping process analysts, business analysts, and process improvement specialists gets started in learning the capabilities of robotic process automation and learning to build their own bots on Automation 360. Users for this track will tend to have the following profile: Familiar with understanding and documenting of business processes. Comfortable with general problem-solving approaches and creative thinking. May or may not be familiar with creating process flows in a software application. Interested in learning the capabilities and use of robotic process automation to automate manual tasks. If the above describes you, then let's get things going! This journey is organized into learning experiences that continue to build on each other: What is RPA?: We’ll give you a quick overview of RPA and Enterprise Automation 360, our web-based RPA platform, and the basics for building on it. Addition

1520
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
My Bot Failed, Now What?

With the rise of Robotic Process Automation (RPA) as an antidote to dealing with the increasing workloads and inefficiency in helping humans complete their digitally-based tasks, there will inevitably be the case where a bot fails. If your bot is simply handling pulling data from other sources, and the bot is well-written—e.g. supports appropriate exception handling—then the user will simply get a notification that the bot did not complete its task and it can be re-run. But what about scenarios in which the bot was updating systems and the bot stalls or fails in the middle of the updates? This is a tricky scenario. RPA is essentially non-transactional, which means that it cannot roll-back changes that have already been made in the middle of a bot execution if the bot cannot complete its tasks. We see this scenario growing not only around RPA but also in the rise of microservices design that calls a sequence of application programming interfaces (API) to update multiple services as part

2260
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Intro To Control Room API with Postman

In this episode of #AAillustrates, we'll discuss what an Application Programming Interface (API) is, have a brief intro to the Automation Anywhere Control Room API, then dive in to setting up and using an Automation Anywhere Control Room API Postman Collection to test different API endpoints. For some additional background, Postman is an API testing/creation collaboration tool that allows developers to test different API endpoints. It's extremely useful for RPA developers to test with so they can understand the proper format for calling APIs, correctly formatting the body of a REST Web Service call, and understand the returned responses from an API endpoint. If you haven't tried it out, you can download the Postman application at Postman.com Full Automation 360 Postman Collection Keep Learning Got the basics of the Automation Anywhere Control Room API down? Great, check out the tutorial on Triggering Bots Using the Control Room API to take the concept even further. In this session, Mic

26990
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Full Bot Build: RSS Feed Reader

In this session, we'll walk through creating a bot from start to finish that can read an RSS feed from wired.com, parse the RSS feed using some commands from the XML Package and Loops Package, and create an HTML page from a template in the referenced GitHub link below. While creating this exact bot build may not be something you have an immediate need for - think about other use cases when your bot may need to parse XML (possibly to read bot settings files, or pass data between bot/sub-task) or create an HTML (building an html based email, creating an html page breaking down the bot run results, or a bot that creates a dashboard based on the logs of other bots). Packages Used Step Package, XML Package, Loop Package, Log To File Package, REST Web Services Package, Datetime Package, Step Package Helpful Links RSS Feed URL: https://www.wired.com/feed/rss GitHub Code: https://github.com/AutomationAnywhere/AAillustrates_RSS_FeedReader Keep Learning Keep the momentum going! If you enjoyed bu

3960
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Quick Tip: Headless Web Scraping

In this session, we’ll look at 2 approaches for extracting text from a web application - including a unique application of the REST Web Services package to perform browser-less web scraping. Video Recap: Recorder Use the recorder in conjunction with the Automation Anywhere Chrome Extension to highlight object on a webpage and extract them. The recorder action does require an established browser session to interact with. Recorder can be a great option for use cases where some navigation through multiple pages is needed or objects on the page are being dynamically loaded at runtime. REST Get Use the REST Get method to read the full page's HTML without the need for a browser - returned as a dictionary - where the Body is the dictionary key to the full HTML text. The String Package can be subsequently used for extracting specific text from the REST response. Bonus Tip When using the REST Get method to return the full HTML of a page or when using the Recorder Capture action to return the in

5670
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
Quick Tip: Advanced String Manipulation

In this session, we’ll look at the String Package and discuss approaches for extracting a sub-string. When extracting data from web applications, OCR'd text from images, or even an Excel file - data unfortunately doesn't always come in the perfect format we need it in - which is why its important to understand how best to extract out the text you need. Video Recap: Extract Text Use the before, before and/or after, or the after settings to extract a sub-string from a body of text. Before: You provide the text that precedes the text you're interested in extracting, and the action will return everything that comes after. Before and After: You provide the text that precedes the text you're interested in as well as the text which comes after the text you're interested in. The action will return all the text that comes between the two. Before or After: You provide the text that may precede the text you're interested in as well as the text which may come after the text you're interested in. T

19140
A
Automation Anywhere Team
A
Automation Anywhere Team
Automation Anywhere TeamAutomation Anywhere Team
published in Pathfinder Blog
QuickTip: Error Handling Basics

In this session, we'll look at the basics of Error Handling in A2019 using the Try, Catch, and Finally Blocks. Remember: Beyond executing the task at hand, your bot's #1 responsibility is to not hard fail leaving a bot runner in a bad state; error handling is the best approach to always being in control of your bots. Video Recap: Try The Try block is for the core code you want to execute. Should everything run smoothly here, the finally block would run next. Should things not run as expected, the catch block would run next. Catch The Catch block is for code that should handle exceptions. This might include logging to a file, saving off a screenshot of the machine's current state, or even sending an email off to a support team. After the Catch block runs, the Finally block will execute. Finally The Finally block is for code that should execute whether an error occurred in this bot execution or not. This block might include things like writing out to an audit log, closing applications th

14400
A
Automation Anywhere Team

Popular tags

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings