Select Option

# Version 141855 **A new release of Sherpa Orchestrator has been released: Version 141855.** 1. In the Form Designer, on the Actions screen, a new widget type has been introduced — HTML/JavaScript, which allows for the implementation of arbitrary interface elements with a unique appearance and behavior. For example, if you fill in the settings window for the element:

Then the following will appear on the Actions screen:

Below is an example with added controls (such as radio and select) and the name attribute to choose between options and implement processing based on the selected value: ```html Select Option

Select Option

Option 1 Option 2

Enter your name

``` When executing this code, you will be able to switch between message output options:

> The code you write in this field can change the appearance of the Orchestrator interface. Use this functionality with caution to avoid unwanted effects. To specify or bind an object's property in HTML, the syntax of double curly braces with a space is used: {{ property }}. A mandatory condition for all input control elements (input, radio, checkbox, select) related to nested objects is the name attribute matching the key name. 2. A new column "Object GUID" has been added to the Audit screen, displaying the GUID of the object mentioned in the record.

By clicking on this field in the desired row of the Audit table, you can navigate to the screen of the mentioned object, where it will be highlighted:

3. Additionally, now all actions performed via the API are also logged in the Audit. 4. In all tables on the Orchestrator screens, the time display format has been changed to \, which improves the readability of the information and makes working with data simpler and clearer for the User. For example,

5. On the Triggers screen, when creating and editing Triggers, a setting "Max monthly runs" has been added, allowing you to limit the number of Trigger activations within a month. For example, if you set the field to 1, then when applying the scheduling option "Every N-th day of the month," the Trigger will activate only once on the specified N-th day.

6. Optional logging of Robot status history has been added. To enable this, you need to add the parameter: `robot_status_logging=1` in the config (`backend/config/config.ini`). The Logs table is available at: `your-orchestrator-address/main/robot-status-logs`.

7. On the Licenses screen, in the license settings, the options "Deny C#, VB, Python and PowerShell code execution within process" and "Force logging in all blocks" are now also available for Unattended mode.

8. On the Jobs screen, a column "Last message" has been added to the table, which displays the last message from the Robot executing the Job.

9. Multiple improvements have been made to enhance system security. --- # 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-141855.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.