# Version 1.40
**A new release of Sherpa Designer has been released: Version 1.40.**
1. The correct operation of Robots and Designer has been tested and confirmed on import-substituted operating systems: [Astra Linux](https://docs.sherparpa.ru/en/sherpa-rpa/ustanovka-sherpa-rpa/ustanovka-sherpa-rpa-na-linux), [Red OS](https://docs.sherparpa.ru/en/sherpa-rpa/ustanovka-sherpa-rpa/ustanovka-sherpa-rpa-na-redos), [Alt Linux](https://docs.sherparpa.ru/en/sherpa-rpa/ustanovka-sherpa-rpa/ustanovka-sherpa-rpa-na-alt-linux), [OSnova](https://docs.sherparpa.ru/en/sherpa-rpa/ustanovka-sherpa-rpa/ustanovka-sherpa-rpa-na-osnova). Adapting the operation of Robots for these operating systems ensures stability, protection of the data used, and versatility of application in various environments, which is important for compliance with security requirements.
2. The ability to run a Robot in [PiP mode](https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-designer/rabota-v-sherpa-designer/rezhim-kartinka-v-kartinke-pip) in hidden (background) mode has been added.
To do this, in the Sherpa Assistant menu in the tray, you need to select the “Robots” item:
Next, in the “Robots - Sherpa Assistant” window, you need to click the button  and select from the dropdown menu: “Always run PiP client in hidden mode”:
PiP client launch settings:
* **“Always run in PiP client mode”** – when this option is enabled, the Robot will always start with the PiP client interface visible to the User.
* **“Always run PiP client locked”** – the Robot starts in a locked state (the PiP client interface is open, but the User cannot influence the Robot's operation).
* **“Always run PiP client in hidden mode”** – the Robot starts, but the PiP client window is hidden and not displayed on the screen.
3. Support for Microsoft Active Accessibility (MSAA) technology has been implemented for working with selectors. The “Record MSAA” button in the “Selector - Edit Selector” window allows you to start automatic recording of all interactions with the user interface using MSAA capabilities.
Click the button  to the right of the “Record” element, and you will have the option to select and click “Record MSAA”:
Microsoft Active Accessibility (MSAA) is a technology based on the COM component model that enhances the operation of applications running in Microsoft Windows. MSAA support allows older programs to interact with modern systems and technologies, improving their performance, increasing stability and accessibility, and facilitating integration with other system components. It is advisable to try using this method of recording selectors if the standard Record button method does not work with the UI elements of your target application.
4. The ability to create your block from the current robot project has been added. To do this, select the “Publish robot as block” option. In the project properties, both input and output data must be specified.
5. The ability to quickly extract (convert) selected blocks into a separate Process has been added, allowing for quick refactoring of the project. To do this, select blocks so that the selected group of blocks has only one input and one output arrow (the number of arrows within the group that do not cross the boundaries of the group does not matter).
Select “Convert to process” from the context menu, and in the “Diagram Name” popup window, specify the name of the new Process.
In place of these blocks, a “Process” block will appear, and the blocks themselves will be placed in the newly created diagram, which is referenced by this “Process” block.
6. The ability to add comments for variables has been added. To do this, right-click on the variable and select “Edit variable comment”.
7. When using the “Bot. Send message” block from the “Telegram” palette, automatic splitting of long messages into shorter parts has been implemented. The post size in the Telegram messenger is 4096 characters. The limit for posts with photos and other media files is 1024 characters.
8. In the “Bot. Send message” and “Client. Send message” blocks in the “Telegram” palette, the property “Message thread” (`message_thread_id`) has been added to specify the ID of the thread to which the message should be sent. This allows sending a message to a specific group within a supergroup, as well as to the comment chat for a specific channel message.
If you are sending a message to a supergroup, then `message_thread_id` refers to a specific group within the supergroup. If you are writing a comment for a message in a channel, then `message_thread_id` refers to the comment thread for a specific channel message. We demonstrated how to determine the `message_thread_id` of the comment thread for a specific channel message in this video:
{% embed url="" %}
9. In the “Client. Create connection” block in the “Telegram” palette, the property “Authorization window timeout” has been added.
10. The block “Modify email properties” has been added to the “Outlook” palette for editing email properties.
11. The blocks “Reply to email” have been added for the “Outlook” and “Exchange” palettes.
12. In the “Write value to cell” block in the “Excel” palette, the ability to set the type “Url” has been added when selecting the value type in the “Properties Panel”.
13. New blocks have been added to the “Lists and Dictionaries” palette: “Dictionary to List”, “List to Dictionary”.
New blocks have been added to the “Data Tables” palette: “Table to List”, “List to Table”.
14. In the “Delete row” and “Delete column” blocks of the “Data Tables” palette, the ability to specify a list of indices for deletion has been added.
15. In the “Save to CSV” block of the “Data Tables” palette, the ability to append data to an existing file has been added.
16. Support for the Chromium-Gost browser has been enabled. Enabling Chromium-Gost support ensures compliance with security standards, increasing the level of data protection.
17. For the “Get value” and “Get credentials” blocks in the “Orchestrator” palette, alternative functions have been added: ‘\_getAssetText’ and ‘\_getAssetAuth’. These alternative functions allow for more flexible and efficient retrieval of values and credentials from the Orchestrator, improving the scalability and adaptability of the system. Examples are displayed in the Expression Editor on the “Output” tab.
18. For the “Execute script” block in the “Remote Desktop RDP/Citrix” palette, the ability to specify call arguments has been added.
The “Arguments” property is filled automatically and only when the “Arguments” button is pressed; manual input is not provided.
19. The blocks “Json Schema Validation” and “Compare Json” have been added to the “Text” palette, which allow for automatic validation of JSON data against schemas and comparison, improving the quality, reliability, and convenience of working with JSON in automated scenarios (including scenarios where JSON is generated by a neural network).
20. The ability to update blocks only from the selected palette has been introduced. To do this, right-click on the palette name and select “Update blocks from this palette”.
21. In the project properties, the ability to specify project settings has been added. The settings are saved not only on the User's computer (locally) but also system-wide — in the Orchestrator, if it is used.
These settings are available through the “Load project settings” and “Save project settings” blocks in the “Orchestrator” palette. The “Load project settings” block returns a variable of type Dictionary.
A detailed description of working with the “Project Settings” dictionary is available in the Expression Editor:
When selecting the Credentials type in the Project Properties on the Project Settings tab, you can pass login and password:
1.
```
```
2.
```
```
Project settings in the Orchestrator are saved as the corresponding Resource type - for logins (login) and passwords (password), Credentials are used, which are stored and transmitted in encrypted form, while for other types of settings - Text. They can be viewed through the Orchestrator interface in the “Resources” tab:
The values of constants can also be seen in the “Resource” window by clicking on the icon :
When the User sets project-level settings (constant, type, and description), these parameters can be reused in other projects if you apply the same constants for dictionary keys. This ensures consistency and simplifies management.
However, it is important to understand that only the specifications of constants, their types, and descriptions are available in the project settings. The actual value of the constant is set separately when used or implemented in automation.
For example: By setting the constants “SMTP\_SERVER” and “SMTP\_EMAIL”, the User can specify the server and port for SMTP, and then use these settings with the same keys in the settings dictionary in other projects.
22. If input parameters are specified in the Project Properties, you can use “Debugging settings” to specify the values of parameters that will be used when running the project in debug mode. By setting the values of input parameters, you can start debugging the project with these input parameters.
23. In the Expression Editor, the ability to specify a path to a folder or file in the expression editing field has been added. To do this, right-click on the expression editing field and select one of the items from the dropdown menu:
* “Select path to folder…”;
* “Select path to file…”.
The path will be inserted into the window at the current cursor position.
24. The ability to check for updates for the Robot and Designer and download it from the website has been added. To do this, select the “Check for updates…” item in the Sherpa Assistant menu in the system tray icon.
Next, if an update is found, you need to click the “Download update” button in the “Update found” window:
Or, if you have the latest version of the program, simply close the window with the message: "You have the latest version of the program":
An internet connection is required to check for updates.
25. In Sherpa Assistant, a function for authorization under a specific Orchestrator User has been added, followed by loading Folders and Processes from the Orchestrator that are available to this User. Thus, the User has the opportunity to use not only local Robots but also Robots to which access has been granted through the Orchestrator.
To do this:
* In the Sherpa Assistant menu in the tray, select the “Robots” item:
* In the upper part of the window, click the “Settings” button:
* In the “Settings” popup window, enter the User's login and password (which is set for this User in the Orchestrator):
* Click the “OK” button.
After logging in, Processes synchronized with the Orchestrator will become available to the User:
They can also be seen on the [Processes](https://docs.sherparpa.ru/sherpa-orchestrator/rabota-v-sherpa-orchestrator/ekrany/processy) screen of the Orchestrator:
The Folder access functionality in the Orchestrator allows:
1. To differentiate access for Users with different Roles to different sets of Processes;
2. To visually separate Processes into different folders, which enhances the convenience of searching for and launching the necessary Processes in the Assistant window.
To use this functionality together with Sherpa Assistant, assign different Access Folders to different Processes in the properties of those processes through the Orchestrator. After that, in the Sherpa Assistant window, the logged-in User will see only those Processes from the Orchestrator to which they have access according to the Roles assigned to them in the Orchestrator and the Access Folders available to those Roles (and accordingly the Processes in those Access Folders). The logged-in User will also see the Processes not in a linear list but arranged in the corresponding Access Folders, as defined in the Orchestrator.
26. In the Sherpa Assistant window, the ability to automatically sequentially launch Robots when starting the program has been added. For this to work, Sherpa Assistant must start simultaneously with the computer boot. To do this, in the settings, on the first tab, you should activate the option "Autostart program with Windows".
The order of launching multiple sequential Processes in autostart is determined by sorting them by name. Therefore, to organize sequential launches, it is recommended to name the Processes for launching Robots with indices, for example:
* “1 robot”;
* “2 robot”.
The Processes will be executed in the selected order, providing convenient and flexible management:
Processes for launching Robots can be renamed directly in the folders:
`c:\Users\User\AppData\Roaming\Sherpa RPA Data\MyRobots\`
> For the autostart to work correctly, you need to go to the “Settings - Sherpa Assistant” window, switch to the “Main” tab, and fill in the checkbox “Autostart program from Windows”:
After that, it is enough to check the checkboxes for autostart in the desired order, and the Processes will be executed one after another.
Processes in this window can also be launched by clicking the button .
27. Other improvements and refinements have been made in various parts of the system.
---
# 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-designer/versiya-1.40.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
