Refers to ElectroNeek Studio - a tool that is used to design an automation workflow.
Refers to ElectroNeek Robot - a tool that is used to execute a designed workflow. The workflow is passed either from Studio or Orchestrator.
Refers to ElectroNeek Orchestrator - a tool for managing workflows. It's a part of a user account in the ElectroNeek ecosystem where the user can schedule workflows on different robots and set up a webhook to launch a specific workflow.
A set of guides, instructions and useful information regarding the functionality of the platform.
Numbers displayed in the title bar of Studio and Robot. They reflect the latest changes in the product. A list of changes can be found on the community forum or in the "Releases" section of the Knowledge Base.
The workspace located in the center of Studio. It is the space where all the activities are placed to form a workflow scheme.
A file of the .neek extension that contains an algorithm of actions to be performed by Robot.
A set of workflows that automates one Business Process. For example, a project "Fill Invoice Data" may contain workflows such as read_configuration.neek, extract_invoice_data.neek, fill_invoice_data.neek and so on.
A particular action/function that is displayed in a rectangular block on the canvas. This action (or function) contains parameters that can be modified according to the process. For example, the Open URL activity performs a simple action - it opens a specified link in a browser.
Properties of a particular activity. These properties adjust the behavior of the given activity to a given business process.
A name-value pair where you can temporarily store the information needed for the workflow execution. For example, a text to be written into some form by the Robot, or the value of the clipboard that you need to paste somewhere.
A variable that is accessible in all .neek files anytime.
Unexpected behavior of a workflow. Many processes require error handling. For these purposes, all activities have the red port used to catch the error.
A graphical space located at the bottom of Studio and used for displaying various status messages such as Task finished successfully and customized messages set in the Log to console function.
Buttons, edit fields, combo boxes and other parts of a desktop application.
A tool that is used to identify and remember desktop applications' interface elements on the screen. The information provided by the Desktop Picker is then used by the Robot to click the right Interface Elements.
Buttons, fields and other parts of a webpage.
A tool that is used to identify webpages' elements on the screen. Similar to Desktop Picker, Robot uses those identifiers to operate the "picked" webpage elements (click, hover, type, etc.)
A result of identifying an interface element or a webpage element. Both Desktop and Browser Pickers display selectors as tables. Practically, the selector is a set of attributes and their values which the Element can be found with
A particular property of a selector. In both Desktop and Browser Pickers, it is a cell in the 'Name' column. This property usually changes depending on a selected element or application.
A process of identifying and removing errors in a workflow. To start debugging, a breakpoint must be specified.
A part (therefore, an activity) in a workflow where the execution must be interrupted while Debugging to see the values of all the variables
Text Recognition Engine
The technology that is applied to perform optical character recognition. It is used for extracting text data from images, usually document scans.
A set of rules applied to an image in order to extract text data from the document. An example of these rules can be a specific area on a picture where the data must be extracted from.
A button that saves changes in the opened workflow.
A button that opens an already saved workflow.
A button that creates an empty workflow.
A profile on the website that contains the user data
Connect to Orchestrator
A button that makes the chosen workflow available for scheduling in Orchestrator.
Disconnect from Orchestrator
A button in Orchestrator that removes the workflow from Orchestrator but does not remove the files on the hard drive.
Rules of when the given workflow must be launched.
In Orchestrator, a way of triggering a workflow to start. If you are interested in the meaning of the term "Webhook," please refer to https://en.wikipedia.org/wiki/Webhook
Organization's ability to use the ElectroNeek Platform according to the Subscription Plan
A Client of ElectroNeek Platform. The organization contains a set of users (typically Client's Employees) and their permissions.
A set of permissions for specific actions within the product. For example, a person with the 'Developer' role has permission to use Studio for development and more.
A set of services/features of ElectroNeek Platform to be used by the Client
Temporary access to the ElectroNeek Platform for the Client. The purpose of the Trial is to discover and try the abilities of the platform
A graphic representation of people's activity on their computers. This dashboard is located in the user account and displays information about which applications were used by the users and how long.
Detailed information and recommendations on which actions can be automated as a result of calculations made by the product
Actions that are performed with a certain level of regularity, potentially to be automated in the future.
Data that provides information about how many actions can be automated and how many hours can be saved in future.
Total time per day when an Employee was using some software. It is built upon Robot collecting software usage information for Employees' computers.
The time when the employee was inactive on the computer.
First time in the day when Robot has first seen any activity on Employee's computer.
A graphic representation of people's activity on their computers. This dashboard is located in the user account. It displays information about which applications were used by the users and for how long.