Julio de 2026

July 2026 release notes for Solutions in Automation Cloud.

July 23, 2026

IXP models available as a solution resource (Preview)

You can now include IXP models as resources in a solution. When you select an IXP model, either from the Extract node in a Flow or through the Use Solution Resource toggle on the Document Understanding Project Extractor and Extract Document Data activities, the IXP model is added to the solution. It appears in the resources panel in Studio Web and is packaged and deployed together with the rest of the solution's resources.

For the full list of components a solution can include, see Solution components.

This capability is also announced in the IXP, Document Understanding activities (3.4.0-preview), and UiPath Intelligent OCR activities (7.4.0-preview) release notes.

July 22, 2026

Link, change, and unlink resources in the resource explorer

The resource explorer now surfaces the link, change, and unlink actions for a component. While customizing a draft installation or a deployment's version change, you can link a component to an existing resource, change which resource it's linked to, or unlink it.

The Link to existing picker now shows the resource kind icon (including connector images for connections), a friendly type label, and the resource's folder location on every row. Personal Workspace locations are labeled My Workspace. When a component is linked, the resource explorer shows a card with the linked resource's information instead of a set of read-only fields, and resources that live at the tenant level are marked with a dedicated icon and a Tenant chip.

Linking and unlinking remain unavailable when editing the configuration of, or activating, an already-installed deployment. In those flows, a notice now indicates when a component is linked instead of leaving the fields ambiguous.

For more information, see Link, change, or unlink a component.

6 de julio de 2026

Corrección de errores

• Fixed an issue where linking a resource from another folder during deployment stored the runtime dependency against the original source folder instead of the solution folder where the resource is copied. This prevented users with permissions on the solution folder but not the source folder from running processes. For more information, check Deploying a solution.