Skip to main content

Types of Recording


Types of Recording:
4 types of recording modes are available
Ø  Basic
Ø  Desktop
Ø  Web
Ø  Citrix
2 ways of Recording
Ø  Automatic
Ø  Manual

Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities.

Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity.

Web – designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default.

Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explicit positioning


Note:
Desktop, Basic and Web Recording toolbars are quite similar and enable you to:
Ø  Automatically record multiple actions performed on the screen
Ø  Manually record single actions, such as:
ü  Starting or closing an application or web browser
ü  Clicking an interface element
ü  Selecting an option from a drop-down list
ü  Selecting a check box
ü  Simulating keystrokes or keyboard shortcuts
ü  Copying text from a UI element or performing screen scraping
ü  Looking for elements or waiting for them to vanish
ü  Finding an image
ü  Activating a window


Citrix Recording toolbar supports only Manual Recording (Single Actions) & enables you to:
ü  Click an image or text
ü  Simulate keystrokes or hotkeys
ü  Select and copy text from a window
ü  Scrape UI elements
ü  Look for elements or wait for them to vanish
ü  Find an image or wait for it to vanish

ü  Activate a window

Comments

Popular posts from this blog

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)

RPA Life Cycle

RPA Life Cycle: It is similar to software development life cycle with some minor changes. Technically, we called it as ‘ Life Cycle of a Bot’   Analysis:           ·     RPA Cycle begins from ‘ Analysis ’ phase.           ·     In this, Business Team & RPA Strategist/Architect identifies business process to automate           ·     After finalizing feasibility on process, implement plan of work (which includes documentation, Resources count & Time  ...) Development:          ·       Dev. Team starts working on requirements wrt to Environment.          ·       We called this phase as ‘ Bot Development ’          ·       Based on Tool selection , Limited/No coding is required ...

Why RPA, Why not Other Tools

Like below there are several features compared to other tools RPA QTP/UFT SELENIUM Commercial Commercial Open Source Less Programming Moderate Programming More Programming License Cost is Less License Cost is More No license cost Free Version No/Minimal additional cost for extra bots Add-Ins Additional cost is very high Free/Paid Add-Ins are available ROI is more ROI is less compare to RPA ROI is more as Open Source Error rate almost to Zero Error rate is moderate Error rate is moderate Customer Satisfaction is high Customer Satisfaction is Moderate Customer Satisfaction is Moderate User Friendly User Friendly Complex 24*7 support 24*7 support No Support