Robolytix

robolytix is the key online analytic and monitoring tool for robotic process automation using sonar technology to evaluate, audit, monitor and improve performance of robots operating on any application or rpa platform getting started with robolytix prerequisites a robolytix account to use robolytix with {{product name}} , it is necessary to have a robolytix account if you do not have one, you can create a robolytix account at robolytix com https //app robolytix com/en/signup connecting the robolytix service to {{product name}} to connect your robolytix account to {{product name}} , follow the general instructions for connecting to services docid\ so88fm6pkt0g adkddfzz when creating a connection, you are asked to provide an api key to get your key, log in to your robolytix account https //app robolytix com/en/login and follow the instructions generating api key is in more detail described in robolytix documentation https //www robolytix com/docs/get api key/ there are two main steps 1\ from the left navigation menu, select settings on the settings page, select api keys in the menu and then click on new api key button 2\ copy the unique key and add a new connection to {{product name}} with this key overview process monitoring process monitoring is performing by using sonar checkpoints the sonars are at the beginning of the process, the end(s) of the process, and any other points in the process between start and end(s) sonar technology the sonar technology allows you to place sonars in any process, including hybrid solutions, processes that use a variety of tools and applications, including possible interaction with people sonars can be located in the {{product name}} process, but also in parts of the process outside of make so you can watch the whole process online, not just the robotic part robolytix collects real time data from all sonars (including those outside {{product name}} ) and represents them as kpis in dashboards actions sonar each sonar embedded in the process contains the following settings connection robolytix docid\ wfhc5evyfojpba0bfkfv9 name the name of the sonar should reflect the state of the process that indicates passing through this checkpoint process select a process from the list the list contains all processes from your robolytix account if you don't see your process in the list, make sure the process you want is existing in your robolytix account type the type of sonar determines its location within the process start is the first checkpoint in the process continuous are checkpoints anywhere in the process of course, more continuous sonars means more powerful statistics end is the last checkpoint in the process the process can have one or more "end" sonars in different branches of the process error is a special type designed to receive error information for specific modules in the {{product name}} {{scenario singular lowercase}} it is inserted by the "add error handler" function of the module start is the first checkpoint in the process continuous are checkpoints anywhere in the process of course, more continuous sonars means more powerful statistics end is the last checkpoint in the process the process can have one or more "end" sonars in different branches of the process error is a special type designed to receive error information for specific modules in the make {{scenario singular lowercase}} it is inserted by the "add error handler" function of the module the type of sonar determines its location within the process process run identification the process run begins with its start, which is the first pass of “start” sonar this process it continues through “continuous” sonars to “end” sonar(s) for advanced reporting, we recommend identifying each separate run process by a unique identifier the unique identifier must be a variable generated by “start” sonar and passed to all other sonars in the process if the process starts in make, we recommend using the “runid” variable of the starting sonar use the following trick to do this while editing the {{scenario singular lowercase}} , run this {{scenario singular lowercase}} to pass sonar "start” successfully, whereby make creates the "runid" variable for this {{scenario singular lowercase}} then edit all remaining sonars in the process the “runid” variable that you add as a unique identifier is available in their settings if your hybrid process continues with sonars in other tools and applications outside of make, you need to ensure that this variable is transmitting if run identification is not set, robolytix stores the total number of sonar passes there are no extended outputs about the time course of such a process however, in some cases, this is entirely sufficient therefore, run identification is an optional setting