Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Solution Tour and Introduction to the Digital Worker administration platform

Agenda

Date

Topic

Contents

Day 11) Getting Started

a. Hardware Software requirements

b. Downloading the tools (STU and PAM)

c. Installation and Sign Up

  • If you have used your email previously for another ARGOS account

       1. Our SV/STU account supports the "email plus(+) sign" scheme when you want to use an email address which has been already used at any other accounts.
       2. For example, new registration with example+2@argos-labs.com is possible after example@argos-labs.com has been used to register an account already.
           The correspondences will go to the correct address
       3. (More here: https://gmail.googleblog.com/2008/03/2-hidden-ways-to-get-more-from-your.html)
d. Logging onto Supervisor
e. Switching on the Plugins

2) STU Overview and Support Resourcesa. Where to get help
  • FAQ from STU (You can access FAQ from our website too)
       1. https://wiki.argos-labs.com/display/RPARELNOTE/FAQ
  • Keyword search
       1. FAQ
       2. Toolbox
  • STU links to help
       1. The [HELP] tab
          a. Benny’s page for Variables
          b. FAQ access
          c. tech@argos-labs.com
             i. 24-hour email support		       2. Help for specific Operations
          a. The QUESTION buttons
       3. Learn More
          a. Variable
          b. Return Value
       4. Time-out
       5. Toolbox
       6. Timeline
          a. Steps
          b. Functions
  • Tutorial Materials
       1. 90 min Rocket Start videos
          a. https://www.argos-labs.com/rocket-start/
3) PAM Settings and Registrationa. Test your PAM
b. Check to see if Supervisor sees your PAM
4) The First Bota. How operations connect with each other
b. How ARGOS Low-code variables work
c. Auto Rec
d. Manual Bot Development
e. Combining Manual Development and Auto Rec
f. Test locally with your PAM		g. Deployment
i. ebot
ii. On-demand remote execution
iii. Scheduled execution
iv. API
h. Execution result at Supervisor
Day 25) Various Automation Capabilitiesa. Bot navigation schemes
    i. API driven
    ii. Code/Object driven’
       1. HTML
       2. JavaScript
       3. Python
       4. PowerShell
       5. Run Program
       6. Window object
    iii. Properties/Windows metadata
    iv. Shortcut Keys
    v. Image Processing/GUI base

b. Triggering the bot execution based on events

  •     By monitoring email inbox
  •     By monitoring a folder
  • Kick-starting from another bot

c. Calling functions
d. MS Excel manipulation options
e. PDF manipulation options

Day 35) Various Automation Capabilitiesf. Web application
    i. Data entry
    ii. Data extraction – Webscraping
       1. Open Browser
       2. Python Selenium
       3. Other plugins
g. Files and folders
h. Sending emails		i. AI-OCR
    i. Google
    ii. Konica Minolta
    iii. others
j. Repeat processes – setting up loops
k. Large data processing
    i. Excel vs Pandas
Day 46) Troubleshooting
  • Supervisor execution results
  • Supervisor Reporting/Notification features
  • How to add helpful built-in execution logs into bots
  • How to isolate the problem (view variables and step by step execution)
  • Tips - where to look first (Windows focus, application delay, real data vs visible data)
  • Try-catch for non-stoppable bot
7) Increasing Stability and Robustnessa. Windows focus/Active application
b. Verification operations
c. App performance/Resource release and use of delays
d. Retry loop implementation and in-bot error notification
e. Custom logs (in-bot) for easier troubleshooting
Day 58) POT SDK – building your own Plugin/Operations This part requires Python coding experience (or any other programming experiences)
  • No labels