# Version 141853 **A new release of Sherpa Orchestrator has been released: Version 141853.** 1. The "Overview" screen now features the ability to create and edit custom Dashboards using the builder located in the "Sections" tab. Users can now add widgets, including options such as "Number," "Bar," "Pie," "Line," and "Timeline." For each created widget, data sources can be configured using both the visual builder and SQL queries. Additionally, the system allows for the creation of multiple Dashboards and management of user access to them, providing flexibility in configuration (a user can have access to multiple Dashboards simultaneously). A demo Dashboard is available in the "Default" tab, illustrating examples of widget configuration. To make the default Dashboard editable, you need to clone it and work with the resulting copy. 2. The maximum number of concurrently running robots (on the "Triggers" screen) now affects the number of Jobs created in the "Create Job without a pre-assigned Robot" mode. This means that the number of Jobs in "Pending" status for a group of Robots cannot exceed the set value of "Maximum number of concurrently running robots," unless it is set to 0. Thus, this setting helps control system load and prevents an excessive number of pending Jobs. 3. On the "Triggers" screen, when creating or editing a trigger in the "Schedule" tab, the ability to specify a time period for the trigger's action within a single day has been added. 4. A "Test" button has been added on the "Triggers" screen, allowing for the automatic creation of a Job based on the selected Trigger with a single click. 5. On the "Triggers" screen, during the creation or editing of a trigger in the "Email" tab, a "Test Email Reception" button has been added. This convenient feature allows you to check the connection to the mail server and obtain information about the number of emails that meet the conditions specified in the Trigger. 6. The ability to store process versions on the Robot's side has been implemented, requiring an update of the Robots to activate this functionality. Now, the Robot will load the process file from the Orchestrator only if it has changed. Otherwise, the version of the process from the Robot's local storage will be used. 7. On the "Robots" screen, a filter by robot type (Attended, Unattended, Coordinator) has been added to the table. 8. On the "Processes" screen, the table has been updated to include columns for "Last Run" and "Link to Last Job." 9. On the "Queues" screen, a "Change Status" button has been added, allowing for bulk changes of the status of all selected Tasks to the specified one. 10. Improvements have been made to enhance the stability of the Orchestrator's reconnection to the database in case of a connection break. 11. In the configuration file config.ini, the option to disable the display of notifications about expiring licenses upon entering the Orchestrator has been added. To do this, simply set the parameter show\_license\_exp\_modal to 0. 12. In the configuration file config.ini, the ability for more precise configuration of the Orchestrator's archive database is now available. These settings are similar to those applied for the main database. You can configure the following parameters for the archive database: * database\_dbname\_archive – database name. * database\_host\_archive – host where the database is located. * database\_user\_archive – username for database access. * database\_password\_archive – password for the specified user. * database\_port\_archive – port used to connect to the database. * database\_engine\_archive – type of database engine used. 13. The Orchestrator now correctly updates the status of a Job that was in "Unknown" state as soon as the Robot performing that task reconnects. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sherparpa.ru/en/obnovleniya/obnovleniya-sherpa-orchestrator/versiya-141853.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.