ElectroNeek Release Version 8.5

We have a new version release 8.5, we have made significant updates on both the User Portal and the Automation Hub.

Here is what we have improved

User’s Portal

What’s fixed?

  1. Fixed a bug where after logging in to the suspended organization, you would be redirected to an empty page.
  2. Fixed a bug where the user’s role would not be displayed in the “Invitation acceptance” event in the audit logs.
  3. Fixed a bug where in the received invitation email, the joining link would redirect you to a non-existent page.
  4. Fixed a bug where after changing the language and pressing “Back” you would not be returned to the previously chosen language.
  5. Fixed a bug where after following the invitation link, you would be redirected to a different page.

Automation Hub

Studio Pro

What’s new?

  1. More information in automatic logs. Enhanced the functionality of collecting logs for each run. Now, the logs will contain more useful information. This information will be included in the log files created using the “Automatically collect logs for each run” option.
  2. Choose dynamic values as input for the Select List Item ( desktop and browser) activity. Now, this activity has a “Calculate a value” option which will let you use variables and, therefore, design dynamic algorithms by interacting, for example, with variable values in the drop-down lists in web or desktop interfaces.

What’s fixed?

  1. Fixed a bug where the selector, created by the Browser Picker, would find the selected unique element.
  2. Fixed a bug where the enabled “Encrypt .neex content” parameter in the Export to .neex option would lead to an error.
  3. Fixed a bug where the Write Word file activity would fail if the text had the Ampersand (&)character.
  4. Fixed a bug where the Convert to image activity would distort images.
  5. Fixed a bug when you were redirected to the Google Chrome extension store when pressing “Install” to install the MS Edge extension.
  6. Fixed a bug when the Combine to PDF activity would throw an exception System.OutOfMemoryException when processing a big number of files.
  7. Fixed a bug where the Open Application activity would fail while opening .vbs files.
  8. Fixed a bug where the Open Application activity would fail if the application was in the same folder as a project.
  9. Fixed a bug, where the launching of the workflow containing Read Excel File, would lead to an Unexpected Error Could not load file or assembly 'System.ValueTuple...' or one of its dependencies error.

Bot Runner

What’s new?

  1. Debug logging. Enhanced the functionality of collecting logs for each run. Now, the logs will contain more useful information. This information will be included in the log files created using the “Automatically collect logs for each run” option.

What’s fixed?

  1. Fixed a bug where Bot Runner would lose token connection.

Orchestrator SaaS

What’s new?

  1. Maintain RDP Session Active Automatically. Now, there is no need to take any actions to execute bots in closed, blocked, or minimized RDP windows. When you want to run a published workflow on a remote machine, you do not need to maintain the active session manually anymore. As of this release, from Orchestrator you can set up credentials to the Windows account where the Bot Runner is installed and your session will become active automatically each time a workflow is about to start.

Note: Currently, this feature is at the beta stage and is enabled by defult to all our cliens. However, within 2 months, this feature will be enabled only for Silver and Gold plans.

  1. Display workflow console logs. This feature allows you to display the content of logs, created by Console log activity, in the Orchestrator.Console logs can reflect the key business parameters of the workflow or the current state of the workflow execution so you can quickly check the performance of the bot and identify unexpected scenarios during execution.

What’s fixed?

  1. Fixed a bug where the API would send inconsistent responses when sending requests with an empty id.
  2. Fixed a bug where the “Stop” button in the “Workflows” page was inactive.
  3. Fixed a bug where the “Bot runner name” sortings would not work as expected on the “Bot Runners” page.
  4. Fixed a bug where clicking on the “View logs” button would cause an error in the browser console.
  5. Fixed a bug where no email notification would be received if the workflow launch was hung or failed.
  6. Fixed a bug when the pop-up message would not appear when clicking “Generate Access Token”.
  7. Fixed a bug where the “Generate Key” button would become disabled after generating a key.
  8. Fixed a bug where the Cannot convert undefined or null to object\n undefined error appeared when launching a published workflow.
3 Likes

I am testing the 8.5 RDP feature and I am looking for clarification. In the orchestrator for the Bot Machine configuration, I have found the RDP tab. What am I filling out? The machine that will connect to machine in the orchestrator I am filling out? Or is this machine going to connect to the machine I am filling out? RDP Connection in Orchestrator SaaS – ElectroNeek Help Center doen’t answer the question.

Example. In the Past I configured “Machine 1” to be my bot runner in the orchestrator. Then I assigned it “job 1”. Now when I go to “Machine 1” to setup RDP “Machine 2”. Is “Machine 1” going to initiate the RDP to “Machine 2” and launch the “Job 1”? Or is it the other way around where I am configuring the Machine that will initiate the RDP to “Machine 1”?

One other question is can we have a parameter to define the resolution (what is the current resolution you are using)? I have found image recognition to be flakey in the past if you change resolutions. Also coodinate clicks on a X,Y will be broken as well.

Hello @benoates, in regards the RDP feature, you are configuring the credentials of the machine that is running the Bot Runner in which you want to run unattended bots. I have recorded a quick video showing how this work: Loom | Free Screen & Video Recording Software | Loom

For the second question recommend reading the following article: Console window small resolution and/or size – ElectroNeek Help Center

4 Likes

Thanks for the clarity. I watched the video and was able to run a bot with the RDP feature that needed UI.

Hi @benoates, We are glad you found the video helpful. Feel free to raise any more questions.