The .neex format allows you to run the created workflow on any computer without having to install Studio Pro. To run an algorithm in this format, you only need the free Bot Runner program installed on your computer. The use of the .neex format allows you to build a system of a so-called attended-automation, when the work of the bot and/or its launching is performed with the participation of a user.
- Create a bot in Studio Pro.
- When the bot is ready - navigate to "File" → "Export to .neex.".
A pop-up message will remind you that Bot Runner must be installed on your computer to run the bot.
- Click "Export". In the file explorer window that opens, you can choose where to save the bot file.
Encrypting .neex files
With the "Encrypt .neex content" checkbox you can encrypt the .neex file. This option will protect the bot file from attempts to read the content by third-party programs.
Launching the bot
After the .neex bot is saved, you can run it by double-clicking the left mouse button. If Bot Runner is installed and running on the computer, the workflow will start. You can also run the workflow directly through Bot Runner. To do this, click the "RUN BOT" button in the "Welcome" tab.
Bots can also be launched via the command prompt. In this case, you can pass some arguments for launching. For example, in the command prompt you can write the following command:
echo This is a test argument > example.txt & main.neex
Such a command will pass the argument to example.txt and launch the main.neex file.
Transferring bots and files
If the Subprogram activity was used when creating the bot (the .neek files), the subprograms will be automatically taken into account in the final file when converting the algorithm to the .neex format. As a result, it is not necessary to additionally transfer the subprograms themselves or perform any actions to make the subprograms work in the .neex file.
Interaction with elements
If your workflow contains activities that interact with desktop elements, web-elements, or terminal elements, you can also transfer only the .neex file to another computer without having to manually transfer the element files or any other files.
Interaction with images
First of all, if your workflow contains activities that interact with images (Click on image, Find image, etc.), then all images generated by Studio Pro, such as screenshots, will be stored in your project folder. Therefore, you do not need to manually transfer images, when converting your algorithm to the .neex format. But most importantly, you can port the generated .neex file to another computer without any issue.
The same is true for any external image, if you transfer them into the project folder. Thus, you can also use the generated .neex file to another computer without any issue.
However, if images are not stored in the project folder, then only the paths to the images are stored. Therefore, when porting the .neex file to another machine, in order for the algorithm to work correctly you will have to somehow calculate the picture paths in the algorithm itself (for example, this can be done by creating a config-file) or to reproduce exactly the same picture path as on the machine where the workflow was developed.
Interaction with files
If your workflow contains actions that interact with files on your computer (Read text file, Append to file, etc.), then the path to these files must either be calculated within the workflow or reproduced exactly on the machine that runs it.