v.26.3.0.12

In this release, we have introduced enhancements and fixed bugs in the following areas:

Enhancements

Machine Template

a. AutoLogon
Introduced Auto Logon functionality for Machine Templates, enabling machines to automatically sign in using the configured credentials. This ensures that the Runner starts and workflows execute without requiring manual login.

b. Auto-Launch Runner
Once the Runner is installed on the system, it automatically launches within 60 seconds of installation.
Behavior Details
• Users must manually follow the Machine Template setup steps to establish the connection.
• Once the XML key is pasted into the designated folder, the Runner automatically connects to the Machine Template.

Bug Fixes

1. Manager URL Not Displayed Correctly
When the Runner was automatically connected to the Machine Template, the Manager URL was not displayed properly in the Profile section. This issue has now been fixed.

2. Assigned and History Tabs Showing Old Data
When the Runner was disconnected and reconnected, the Assigned and History tabs incorrectly displayed old data. This issue has now been fixed.

Action Required

1. If the Runner was auto updated, or if you have installed the latest version, the existing automation workflow will fail. In this case, you must follow these steps:
a. Update the Designer.
b. Update the corresponding activities in your workflow.
c. Republish the workflow in the Designer.
d. Execute the workflow in the Runner.
Note: If you continue using existing versions of the Runner, they will work without affecting execution and no action is required.

Limitations for Machine Template

• The Machine Template XML must be downloaded from Robility Manager.
• The MachineTemplate folder must be created manually inside the Runner directory if it does not already exist:
   C:\Program Files (x86)\RobilityRunner\MachineTemplate\
• The downloaded XML file must be copied into the MachineTemplate folder.

Limitations for Runner

• Resolution Settings Enforcement: Resolution settings configured in Robility Manager are applied only when using the Auto Logon option. If the system is manually unlocked via RDP, these settings will not apply immediately and will take effect only after restart.
• Starting from version 25.8.0.1, a parameter has been implemented to validate the license key connection. As a result, existing license keys will not work and cause connection or execution failures. Click here to learn more.
• Workflow Initiation Delay: When a workflow is triggered from Robility Manager on a logged-off or locked machine, it may take up to 2 minutes for the status to update to “Run Initiated.”