Orchestrator component

Improvements

  • Improved access restriction to system objects, now only objects to which the user has access are displayed in the "Hosts", "Robots", "Running robots" and "Launch history" sections

  • Added the ability to work with the resource queue. You can create a queue, view the list of resources in these queues, and change resource parameters in the new section "Resource queues". Only robots can add resources to the queue using actions from the "Orchestrator" group

  • Added a new type of robot launch condition - based on resource queues. Now the robot can be launched depending on the availability of the required number of resources in the queue. You can create, view or change such a launch condition on the new "Resource queues" tab in the "Launch conditions" section
  • We have added the "Launch conditions (Resource queues)" tab to the account card of the host. This tab displays only those launch conditions that specify the machine group to which the host account in question has been added
  • Changed the handling of RDP sessions. Previously, the system terminated the RDP connection immediately after a robot was finished. This was inconvenient if there was a short time between the end of one robot and the start of another, and you had to launch an RDP session again. To reduce the time spent unnecessarily enabling/disabling RDP sessions, the system will not terminate the RDP session immediately after the robot finishes, but will wait for a new robot launch within a set timeout period. You can set the required timeout in one of the system configuration files
  • Added columns:
    • "Launch method" and "Initiator" to the table on the "Running robots" tab of the host account card
    • "Author" to the table in the "Robots" section
    • "Author" to the table on the "Schedules" tab of the "Launch conditions" section
    • "Author" to the table on the "Calendars" page (opened via the "Schedules" tab of the "Launch conditions" section)
    • "Launch method" and "Initiator" to the table in the "Running Robots" and "Launch History" sections
  • Several cosmetic changes were made to the interface design of the "Orchestrator" module


Fixes

  • Fixed a bug where when launching a robot via the Orchestrator UI, the agent on the selected host would sometimes not receive the launch command
  • Sometimes the host account continued to display as UI (= graphics session active) even if the graphics session was already inactive
  • Fixed an issue where robots would occasionally "hang" in Launch status if they were launched as part of a process from a ROBIN Process with automatic host selection

"Access control" module

Improvements

  • Redesigned the ability to log in as a domain user. Such users are created and controlled on the side of your Active Directory
  • Changed the transition to the user card - now it is by clicking on the user's login, not on his/her full name
  • Added the ability to group some system objects to restrict access to them within the tenant. In this regard, the following were added:
    • "Object groups" section, where you can create groups and add objects to them to which you want to restrict access. You can create groups for hosts, robots, and robot projects. As well as groups of processes and screen forms - objects that belong to ROBIN Process
    • You can add the "Access control" tab to the user group card. On the tab, you can specify to which object groups the user group in question will have access

  • Changed the "Add host" window in the "Tenant objects" section:

    • Removed the radio buttons for selecting the current location of the host

    • The "Host" field is always active. It only displays hosts whose accounts have been added to the Robin database but have not yet been added to a tenant or tenant group

  • Several cosmetic changes were made to the interface design of the "Access control" module

  • Нет меток