# Version 141848

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

1. A new "Actions" section has been added for constructing web forms that allow business users to create and modify tasks in queues, thereby assigning new tasks to robots or checking and correcting intermediate results of robot work in end-to-end business processes. The functionality includes an "Actions" screen, a form builder, and a separate interface for business users, which opens via direct links created for each action.
2. The ability to enable job creation in the trigger settings after the robots of the selected group are freed has been added, in case they were all busy at the time the trigger was activated.
3. The "Processes" screen has been enhanced to specify the minimum version of Sherpa RPA Runtime required to run this process.
4. The ability to periodically export old jobs, logs, and tasks to an archive database with the deletion of these records from the "production" database has been added.
5. A "File URL" tab has been added to the "Storage" screen when editing files, containing a direct link to download the file from the server. This link can also be used to embed images and PDF files into the corresponding action builder widgets. For example, a robot can upload the original PDF file to storage and create a task in the queue with the result of its recognition, while the business user in the action form will see both the original file from storage and the recognition result from the task fields, and will be able to edit this result.
6. The ability to disable automatic table updates on the Orchestrator screens has been added.


---

# 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-141848.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.