ROBIN Studio

• Fixed a bug where the Studio could use server connection data from the wrong source, now the Studio gets all connection data from the ROBIN Studio server Low-Code mode.
• Fixed a number of bugs when publishing actions, now the publishing process should complete without errors and no duplicate versions of the action should appear.

ROBIN Management Console

• The "Accounts" tab has been returned. Here you can create an account that can be used to run the RDP service.
• When launching the robot with account selection - the account created in the corresponding tab must be used.
• If there is an inactive account on the host, when you try to launch the robot there, an RDP session will be established using the data of the selected account.
• If the account on which the robot is launched is active, an RDP session will not be established.
• RDP connection will use the default resolution set in the application settings on the server.
• When configuring a scheduled launch, the accounts created in the corresponding tab must be used.
• A robot launched by schedule behaves similarly to a manual launch - Orchestrator automatically detects the need to launch an RDP session when the robot is launched.
• Signs of an inactive account on the host:
  • The user's session is disabled or inactive (if the RDP connection has been terminated, the user has been logged off, or the PC has been rebooted).
  • In the "For all users" option, a particular user's player is not running.

"Orchestrator" action group

• The "Get element by condition" action has been improved:
  • Now terminates with an error if no resources were found.
  • Fixed an error that occurred when searching for an item by creation or update date.
  • Improved the "Get a collection of elements" action:
    • Fixed an error that occurred when searching for an item by creation or update date.
    • Fixed an error that occurred if the number of items was not specified, even if the "All" rule was used.
    • Improved "Update element" action:
      • Fixed a bug that occurred when trying to modify a read-locked item, now only a write-locked item cannot be modified.
      • Fixed an error that occurred if a default date value was specified in the "Read/Write unlock date" parameters.
      • Improved "Finish element processing" action, fixed an error that occurred when trying to modify a read-locked element, now only a write-locked element cannot be modified.