Glossary

Follow

A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y -

 

The list below gathers and describes the vocabulary used in BizRobo!.

Descriptions in the BizRobo! Knowledge Base mainly use abbreviations; so please refer to the list below if you do not understand a term. (e.g. "RoboServer" is mainly written as "RS")

More details about BizRobo! products are accessible in the First Steps Guide. If you consult it in parallel, your comprehension will improve.
BizRobo! First Steps Guide (Scroll down and download the corresponding document)

 

A

Action

Type of order a step executes.

This is the process each step defines in "Action".

In Bizrobo!, you have access to more than 100 types of Actions; they let you execute a variety of processes.

Add Attribute Window

It is a window that appears after you click the「+」button in the lower part of the attribute table, and it allows you to set the "Name", "Attribute Type" and "Default Value" attributes that compose the type.

1.png

Attribute Table

Area in the upper part of the Type Editor that displays the attributes composing a type, and where you can enter the attributes' initial values.

2.png

Automation Device (DA terminal)

Accessible with the Desktop Automation (Device Automation) function, it is the PC or Virtual Machine (VM) where you want to automate desktop applications in; in other words, a terminal operated by one of your robots.

Automation Device View

Area of DA that displays open applications as tabs, and the element trees that structure each of those windows.

3.png

Automation work flow

Orderly executed series of steps inside a "Desktop Automation" ("Device Automation") step.

4.png

 

B

Branches

Group of steps stemming from junctions (branching points) that are created when robot steps diverge from each others. In the figure below,  [ B → C ] and [ D → E → F ]  are branches.

branch.png

You can place a branch immediately after a selected step if you click "Add Branch from Selected Step".

5.png

Once the upper flow is fully executed, the flow moves on to the lower line.

If you place a a branching point before a loop, the steps of the lower line are run only once the successive loops are completely achieved.
<Reference>How does the running sequence of steps function on DS?

Browser Tracer

You can use it if you select "Tools" in the menu bar of DS. It can trace HTTP traffic, or the execution of JavaScript by robots created in the Classic browser (was by default in versions 9.3 and lower).

6.png

 

C

Classic Engine

Proprietary browser rendering engine developed to emulate to its closest IE8 behavior. It is also the standard browser engine until BizRobo! Basic v9.2.

Complex Type

Temporary storage area to define in advance in the Type Editor. You can set multiple variables and attributes. 

8.png

Configure Attribute

You can display the "Attribute: Configuration" dialog box and edit the settings of the created attributes if you click the "Configure Attribute" button in the lower panel of the Attributes table or if you double-click the attribute of your choice.

1.png

Current Step

Step selected by the user. It is displayed with a faint green color such as in the figure below (or a blue one), and its settings information are normally visible in the Step View.

current_step.png

 

D

DB (Database)

Area to save (file output is also possible) execution logs of robots executed in RoboServer or audit logs that record operations performed towards MC.

<Reference>What are the 3 types of databases used in BizRobo! Basic?

Database View

The area in the bottom left corner of the Robot Editor that lists the databases the robot can connect to.

7.png

Debug Mode

Mode to debug in Design Studio part of or all the robot you have built. You can check whether the robot you have created has been correctly executed or not.

9.png

<Reference>Basics of debugging

Design Mode

Mode to create and edit robots.

10.png

DS (Design Studio)

One of the main tools in BizRobo! Basic and the integrated development environment to create robots. It allows to: create and define robots, types, snippets, and Device Automation; to debug robots; and to upload them to Management Console.

DSS (Design Studio Seat)

Number of allowed simultaneous launch of Design Studio. There is no limit in the number of terminals you can install Design Studio in, but the number of simultaneous executions is set by the Design Studio Seat of your license. (the standard number for BizRobo! Basic being 10)

DA (Desktop Automation or Device Automation)

Feature present since ver.10, it is a step to add in the robot flow to for example automate desktop applications.

It can even automate applications (Windows applications, Java applications, SAP, OracleEBS) and terminals (tn5250/tn3270/vt100) you could not automate on DS.

Before ver.10.4, this action was called Device Automation.

0.png

DAS (Desktop Automation Service or Device Automation Service)

Added since ver.10, this feature is a client software you must install in your PC or virtual client controlled by DA. It manipulates desktop applications internal to the DA terminal following orders from RoboServer. Before ver.10.4, it was called "Device Automation Service".

▼DAS icon

 32161_33.png

Device Mapping

One method to connect Design Studio (RoboServer) to a DAS terminal (Automation Device). Register in advance the information of the device(s) you want to connect to and when executing, the robot will refer to the device information registered in MC and connect to a DAS terminal with an Available status.

Because it is important to define in advance the DAS terminal information to be used by the robot, you cannot define or change the connection target for the DAS terminal while the robot is operating. That is why the reference methods you can use are limited to "Static Reference".

Besides, MC can check the operating status of all the DAS terminals at once as they regularly send their personal information to the MC specified in DAS and update the devices information (Admin > Devices).

The target DAS terminals are ordinarily used when they are logged in, but they can also be operated through the RDP connection of Open steps when the screen is locked. You can also preserve security by manipulating DAS terminals with a locked screen maintained by the Lock Screen function of DAS.

 32161_20.png

※If executing from MC(RoboServer), the "Design Studio" part of the figure above becomes "RoboServer". keyword: Device Mapping Method

<Reference>
Relationship between the connection mode of a Device Automation terminal and the reference method from a robot.

Do I have to use a remote desktop (RDP) to make a robot access an Automation Device terminal?

Direct Connection/Access

One method to connect Design Studio (RoboServer) to a DAS terminal (Automation Device). Specifies the information of the device to connect in a device file (.device) or in a "Connect to Device" step, and establishes a direct connection without passing by Management Console.

If you connect with a "Connect to Device" step, you can specify or switch the device to connect to while the robot is operating. However, you cannot centrally manage and check the total number of DAS terminals and their operating status (Offline/Available/In Use) because the devices information is not registered in MC. With this method, you should select the "Single User" mode in DAS and set the Token information.

With this method you can use both "Static Reference" and "Dynamic Reference" but you are limited to "Dynamic Reference" to run robots from MC(RS). (when using a "Connect to Device" step)

32161_16.png

※If executing from MC(RS), the "Design Studio" part in the figure above becomes "RoboServer".

<Reference>Relationship between the connection mode of a Device Automation terminal and the reference method from a robot.

 

 E

Element Tree

Displayed information structured as a tree and that analyzes the screen composition during the automation of a Windows desktop application with DA.

11.png

End Step

Step that indicates the end of a robot process. When it becomes the current step, it means that all steps of the process (before) have been executed.

end_step.png

 

F

Finders

To use when searching for tags of HTML/XML pages, ranges of cells in a spreadsheet document, or JSON-structured elements.
They are important to specify in steps which part of the page the robot should carry the process to.

<Reference>What are finders of action steps in DS?

Frames View

Area in the bottom right of the Robot Editor, under Step View, that displays a frame made of each screen the robot has loaded. You can also display your frame choice.

12.png

 

G

Global

You can make a variable global by checking the box next to "Global" when setting a variable for a robot in the Variable View. Variables set with "Global" keep their value notwithstanding eventual loop processes or branching points.

13.png

 

I

Installation Folder

Folder where the running module of BizRobo! Basic is installed. With the default settings, this folder is generated at the following location (for Kapow v10.2.0.3 (64bit)): C:\Program Files\Kapow 10.2.0.3 200 x64

ISA (Intelligent Screen Automation)

Feature present since ver.10.3, it can automate applications for which the effects of automation APIs such as Citrix are limited, or applications that cannot be used.

<Reference>Description of ISA (Intelligent Screen Automation)

Iteration

"Iteration" means "repetition". You can store in a variable the number of loops if you use a "Get Iteration" step.

 

K

Kapplet

Feature within Management Console that provides a UI to help end users run robots. They can indeed freely run robots from kapplets using their web browser.

They can also customize them according to the vocabulary they use, but also add icons and explanations.

KCU

It stands for Kapow Compute Unit. It is an indication that logically defines the volume of orders (Actions) a robot can process per second. KCUs are made of KCU points, and 5,000 KCU points are attributed to 1 KCU.
Orders (Actions) that can be set in a robot, consume KCU points according to the process content of each one of them.
If the written KCU is not enough relatively to the actual number of robots operating on the server, an error will not occur, but the robots overall speed will decrease. You will hence need to consider increasing the KCUs if the number of robots running simultaneously increases too.

<Reference>What is KCU?

 

L

License Server

Unified mechanism to manage licenses within Management Console. Production keys and Non-Production keys are registered as license keys, and the robot server runs robots according to the upper limit in process capacity (KCU: Kapow Computing Unit) internal to the License Server.

Besides, it always connects to the License Server when Design Studio is launched and checks the license validity and the number of users simultaneously connected.

Lock Screen

A feature of DAS that lets a robot manipulate a DA terminal with a locked Windows screen.

By logging in a second time in RDP to a session under connection, DAS disconnects the existing session and locks the displayed screen of the DA terminal. However, because the login status in RDP is maintained by DAS, the process internal to a DA step of DS/RoboServer persists.

On the other side, in an environment that automatically locks an active desktop after a fixed time such as for a screen saver, the desktop information displayed by the RDP session within DAS also becomes locked, making impossible to get the screen element tree from DS/RoboServer, hence creating a Finder error when the robot is running. Please turn the screen saver function OFF to set your DA terminal.

To use the Lock Screen feature, a connection permission to RDP (Remote Desktop Protocol) needs to be granted to the user logged in the Windows session where DAS is operating.

 32161_34.png

 

M

Management Console

Central environment for managing robots. It is an application that manages the settings and logs of run schedules of robots developed on DS, but also the robot files as repositories (.Robot, .Type) as well as externally input files. It also sends a notification when an error occurs.

  • You can make Tomcat a Web container, separate Management Console from RoboServer and operate it.

Menu bar

Uppermost area on DS that gives you access to the DS menu.

14.png

My Project View

Area displayed in the upper left part of the Robot Editor. It displays in a tree structure, robot projects open on DS. To be used when creating new robots or types under one folder, or when opening a previously registered robot.

15.png

 

P

Project

Robot management unit and resource shared area where each robot is individually created and run. Resources for types and snippets created on Design Studio can only be shared under the same project.

On Management Console, you can also manage (for each project) schedules, repositories, imports and exports.

 

R

Repository

Area prepared in Management Console to manage (for each project) robots and types, snippets, resources (files for parameters), definition data for DA terminals used with the Device Mapping method, or encrypted passwords.

RS (RoboServer)

Software to run robots from a remote client.
Use calls from the scheduler in MC, REST, SOAP, Java, .NET API, or Kapplets, to run a robot.

RoboServer Settings

Tool to set RoboServer.
You can choose the overall BizRobo! Basic settings such as setting DB or logs, setting the ID and password to access proxy servers or MC, or registering clients certificates.

※Each setting for DS can be set in the "Settings" screen in DS.

Robot

A robot is a program designed to execute tasks related to a data source (usually a website, but Excel documents and databases are also applicable).

In general, for each data source, one robot is attributed per task. For example, you would be creating three different robots for each of the following tasks: extracting news form http://cnn.com, extracting news from http://yahoo.com, extracting products information from an online products catalog.

While automatically performing all the actions that can be done in a browser, a robot can basically combine processes such as extracting or storing data from or in databases and Excel documents.

Robot Editor

Feature to create and edit your robots process flow, and to debug it.

16.png

Robot View

Area in the upper part of the Robot Editor that displays the robot whole structure (flow).

17.png

 

S

Shared Project View

Area in the central left part of the Robot Editor that displays in a tree structure the many projects (robot execution and management units) of Management Console connected from Design Studio.

If a project in the Shared Projects View is shared on DS, it is displayed in both My Projects and Shared Projects.

18.png

Simple Type

Single-attribute type that does not need to be defined in advance in the Type Editor but can be defined each time in the Robot Editor then used. Variables are registered individually and can only be defined with one attribute. As for complex types, you can make simple types have a global characteristic by checking "Global", but you cannot set them as the targets of "Return Value" or input in them a value from an external program.

19.png

Step

Smallest unit for orders executed by robots.

 32161_11.png

Step View

Area displayed in the central right of the Robot Editor, under the Robot View, and it shows the current step settings.

20.png

 

 

T

Text Editor

Feature that can create and edit text files such as Readme files or memos about robots under creation.

21.png

Type Editor

Feature to create and edit fields to temporarily store information about variables (types) used when robots run processes.

22.png

 

U

Unnamed Step

Step with no action set yet.

23.png

Use as Input

To use a variable as an input, check the box next to "Use as Input" in the dialog box that appears when you want to set a variable for a robot in the Variables View.
The variable that has been set as an input can now be used as an entry value when inputting it into a robot.

24.png

 

V

Variables View

Area displayed in the bottom right corner, under the Step View, and that shows the variables used by your robots.

25.png

 

W

Webkit Engine

Present since ver.9.3, this browser engine builds a robot that uses the same browser engine as Google Chrome and Apple Safari. Compared to the traditional Classic Engine, processing JavaScript is much faster but the memory consumption is more important. However, it does not function normally with some websites that exclusively use browser engines different than WebKit, such as IE or FireFox. (8GB or more of RAM is necessary)

Windows View

The area displayed under the Robot View. It displays the screen controlled with the selected steps.

26.png

 

 

 

 

1 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.