Jidoka SDK

A professional SDK (Software Development Kit) is available for companies with their own software development teams that wish to build Software Robots using the Jidoka technology, providing full control over the development and testing cycle. The principal requirement for a developer is to have Java programming knowledge and notions of Maven, since the latter is used for creating robots using archetypes, as well as for packaging and distribution.

Modular

Modular

The API has a modular structure and is designed to provide the developer with the necessary interfaces to extend the basic default-supplied robots and to adapt them to the specific data sources required in each situation of a workflow: databases, files, web services, etc.

Development guided by workflow

Development guided by workflow

The Jidoka robot is based on the execution of tasks and transitions defined on a workflow. The console includes a visual environment for defining the set of actions and transitions for process modeling.

Compatible with any IDE

Compatible with any IDE

Jidoka is not limited to any specific development IDE. Robots can be built using the developer’s usual IDE (Eclipse, Netbeans, etc.).

Centralized repository

Centralized repository

Once we have developed the robot, we deploy it on a Maven code repository, allowing earlier versions to be used if necessary.

Remote debugging

Remote debugging

Robots can be either developed on the machine where the robots are to be executed or on any other physical or virtual node or machine. In both cases, the developer can connect the Java debugger to the node where the robot being developed is located, or insert breakpoints as if it were a standard Java application.

Integration API

Integration API

Jidoka supports integration in other ecosystems, for example, with advanced analytics or artificial intelligence applications. Through the API REST, a user can execute a robot, measure the results of the execution, obtain the artifacts and files generated by the robot and, through the actions and events system, notify other users of events, or even launch a robot in response.

Element Inspector

The element inspector tool allows the developer to identify the element attributes of the applications with which the robot will interact (buttons, text boxes, menus, etc.). Attributes will vary depending on the strategy we are using to build the robot: keyboard commands, use of Windows API, image recognition (Hawk-eye), etc. The tool includes an option to select visual elements with a simple click of the mouse.

Libraries

Jidoka permits the creation of libraries known as nanorobots, which contain specific predetermined actions that later may be used directly in a robot’s workflow, significantly reducing development time. Examples of these libraries are system logins (SAP, Siebel), VPN or proxy connections, or even libraries that access certain application windows. In addition, because Jidoka is developed entirely in Java, you can use any of the thousands of libraries available for this language.