# Version 141852

**A new release of Sherpa Orchestrator has been released: Version 141852.**

1. A new "Object Folders" screen has been added, allowing the creation and editing of access folders that provide a more detailed way to restrict access to Orchestrator objects for different user roles. Additionally, an "Access Folders" filter has been added to the top panel of the Orchestrator, allowing screens to show only the objects located in the selected folder.

**Note:** *Objects for which no access folders are selected are considered to be in the root and will therefore be shown to all users whose Roles have access to the screen of that object.*

2. The "Roles" screen now includes the ability to set access rights for a role (users assigned to it) to specific "Access Folders." When creating and editing Orchestrator objects (Robots, Processes, Packages, Resources, Storage, Queues, Actions, and Triggers) on the corresponding screens, a specific "Access Folder" can be assigned for the selected object.
3. The "Robots" screen has implemented the ability to change passwords for robots in bulk using the import function from a file. When exporting robots to a CSV or XLSX file, an empty "NewPassword" field is added; if a password change is needed for a specific robot, this field should be filled in. Upon subsequent import, the robot's password will be changed to the one specified in the "NewPassword" field.
4. On the "Licenses" screen, when creating and editing "Attended Floating" type licenses, the ability to prohibit the execution of C#, VB, Python, and PowerShell code in scripts run by users whose robot is working with this license has been added.
5. On the "Licenses" screen, when creating and editing "Attended Floating" type licenses, the ability to enable forced logging in the Orchestrator of all blocks on the robot side has been added. This function should be used with caution, as enabling it leads to increased load on the Orchestrator.
6. For the "Actions" screen within the "Form Designer," the interaction of users with Task parameters has been redesigned. Parameters that were in the Task but not used within the "Action" will not be overwritten. Additionally, the Orchestrator will warn about overwriting when editing a Task from the "Action" if the parameter types (table, text, hash table) used in the Task differ from those used in the Action.
7. The interaction of robots with resources of the "Attributes" type has been fixed.


---

# 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-141852.md?ask=<question>
```

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.