2.2510.2

Release date: April 15, 2026

更新内容

Solutions in Studio Web

Studio Web on Automation Suite 2.2510 now supports solutions — a unified developer experience that brings together all automation projects and their dependencies into a single, end-to-end development lifecycle. This includes full support for app projects inside solutions, allowing you to combine apps with RPA workflows, agentic processes, agents, and API workflows within a single solution.

A solution groups everything needed to automate a business process, including the resources they depend on (queues, assets, storage buckets, connections, and more). You can design, debug, and deploy an entire business process as a single package, directly from Studio Web.

主な機能は以下のとおりです。

• Solution Explorer — manage multiple projects and their files from a single view.
• Resource Explorer — define and share resources across projects within a solution, without leaving Studio Web.
• Unified debugging — automatically provision resources for debugging sessions, with a dedicated debug folder created in your Personal Workspace.
• Publishing and deployment — publish solutions as ZIP packages and deploy them to Orchestrator tenants or your Personal Workspace in one operation.
• Version control — use snapshots for cloud workspaces or Git integration for local workspaces.

For details, refer to the Solutions chapter in the Studio Web user guide.

改良点

• We improved performance by removing the automatic codebehind state save that occurred every 30 seconds. If an unexpected failure occurs before the 12-minute threshold, a message now prompts you to reload the page.
• The app published versions previously had a hard limit of 150 records. We are now allowing you to retrieve more than 150 published app versions.

バグ修正

• Previously, PDFs were not displaying in the Document Viewer control in certain scenarios.
• An issue caused documents with page numbers to fail rendering in the Document Viewer control.
• An issue occurred when an app task was in an unassigned state. In this scenario, the Document Viewer control was not scrollable.
• Previously, the Document Viewer was not scrolling to the correct page for PDFs with a generic content type.
• Previously, the Document Viewer extended to full width even when the width property was explicitly set to 50%.
• An issue caused the File Upload control to not retain the allowed file types setting in Safari.
• Previously, uploading a file to an entity from a custom list was failing.
• An issue caused files uploaded using UploadFileToStorageBucket to get corrupted intermittently.
• Previously, app performance was degrading over time when using entities extensively.
• An issue caused app jobs to take an unusually long time to complete intermittently.
• An issue caused the handshaking process to not complete within the expected 30-second timeout intermittently.
• An issue caused codebehind jobs to keep running for 15 minutes without completing state transfer.
• Previously, ContentValidation (DU) action property data became empty after a job state transfer.
• Multiple unhandled edge cases in state transfer were causing unexpected behavior.
• An issue prevented the validation station app from opening within a custom app.
• Previously, a client-side error prevented users from viewing action tasks.
• An issue was causing the creation of inline escalation apps using Autopilot to fail.
• Previously, Apps Studio failed to load for VB apps.
• An issue caused a solution app to return an "app not deployed" error at runtime after an upgrade.
• Previously, an error occurred when downloading a Studio Web solution that contained apps.
• An issue caused the link between a form and its load event XAML to break, leading to unexpected behavior at runtime.
• Previously, app jobs failed if a trigger or RPA workflow was already in progress.
• An issue was preventing solution activation from triggering tokenization for VB apps.
• An issue caused the Edit Grid control to get stuck in a loading state after a data update when placed inside a modal popup.
• Previously, the app versions package URL contained an extra slash, leading to incorrect URL resolution.
• An issue caused the folder key and tenant key to not be cleared from runtime session storage for remote apps.