How to bring Auto Rec output to a deployable bot

Auto Rec Optimization Team: 2 members

1. Subject Matter Experts (SME, LOB, or Citizen member) - Someone who is knowledgeable about the target process - Usually, the one performing the target process while running the Auto Rec in the background

2. Scenario Optimization Experts (SOE, IT, Software Engineer, or STU Operator) - Someone who understands software optimization and will convert the Auto Rec output to a deployable bot using ARGOS STU.

Need help?

Technical inquiries contact to tech@argos-labs.com

Contents

• Step #1: Observe Screenshots and Properties

• Step #2: Manage delays

• Step #3: Mouse click corrections

• Step #4: Key stroke corrections

• Step #5: App title/name optimization

• Step #6: Integrate App Start/Switch operations

• Step #7: Apply basic Application plugins

• Step #8: Test Run and Happy Path review

• Step #9: Bot development and stabilization

• Step #10: Volume Test and Optimize Performance

• Step #11: Fix and finalize the bot

• Step #12: Documentation

Step #1: Observe Screenshots and Properties

 This is a discussion session between someone who performs the target process (the Subject Matter Experts (SME)) and someone who will convert the output to a deployable bot (the Scenario Optimization Experts (SOEs))

• Jointly observe the Screenshots in slideshow mode and the property data

• Objectives are:

Open

Step #2: Manage delays

 This is a SOE task

• Use STU Settings menu for one-click change-all feature

• Extend delays on

Open

Step #3: Mouse click corrections

 This is a SOE task

• Find back-to-back mouse click (Locate Image) operations and, if applicable, consolidate multiple single-clicks into double/triple clicks

Open

Step #4: Key stroke corrections

 This is a SOE task

• Observe the [Shortcut Key] operations and convert them to Text Input when applicable (use the paste option when applicable)

Open

Step #5: App title/name optimization

 This is a SOE task

• Go through [Locate Image] and [Image Match] operations and remove non-consistent values from app titles and app names

• If applicable, replace them with “*” wildcard

Open

Step #6: Integrate App Start/Switch operations

 This is a SOE task

• Find when applications start and see if you can use [Run Program}

• Find when applications are switching and see if you can use [Select Window]

Open

Step #7: Apply basic Application plugins

 This is a SOE task

• See if you can apply [Excel, PDF, Text, File/Folder] plugins for quick stabilization

Step #8: Test Run and Happy Path review

 This is a joint task between SME and SOE

• Run the scenario in the actual environment

• Objectives are:

Step #9: Bot development and stabilization

 This is a SOE task

• Perform the following and bring the bot to deployable state

Step #10: Volume Test and Optimize Performance

 This is a joint task between SME and SOE

• Bring the prototype bot to a test environment and repeat test

• Objectives are:

  • Discover more exceptions and errors

  • Minimize delays to optimize performance

Step #11: Fix and finalize the bot

 This is a SOE task

• Implement the findings from Step #10 and make the bot more robust, stable, and fast

Step #12: Documentation

 This is a joint task between SME and SOE

• Put together “User’s Manual” for the bot

• Should include

  • Description

  • Development team names and contacts

  • Input and Output

  • Deployment environment and execution schedule (triggers)

  • Logs format – where to find them and how to read them

  • Trouble shooting guide