The 2025.10 release introduces one new feature and six fixes.
FEATURE: Custom work queue screens
Work queues can now use custom-designed screens instead of automatically generated layouts with just fixed list of “tabular” data. Now for example, documents, email attachments, etc. can be displayed. This enables tailored user interfaces for different queue types and improves usability in manual processing scenarios.
Developers can specify a screen name in the CustomScreen field of a Work Queue definition.
If provided, this screen is used to display queue entries, allowing full UI customization while keeping data binding handled by the Work Queue Class. You can find out more in the documentation.
FIX: Blob download error when filename contains non-ascii char
We resolved a bug where downloading or displaying a a file content (like attachment) failed if the file name contained non-ASCII or control characters.
FIX: Procedure OrigamIdentityGrantCleanup on PostgreSQL failing
We fixed an issue causing the procedure to fail with “more than one row returned” when multiple records were processed.
FIX: Deployment fail error message not pointing to the cause of the error
When Architect opened a model with broken dependencies it did not always show the real cause of the problem in the error message. With this fix we improved the error messages during deployment sorting to clearly identify the cause of issues. Previously, circular dependencies or missing references were not explicitly highlighted, making troubleshooting difficult. Now, the system provides clear indications of blockers, such as:
Blocker: Workflow 1.1.0
Dependencies: Root 5.3.1
This enhancement aids developers in quickly identifying and resolving deployment dependency issues.
FIX: Failure workflow step not executed after failed UI step
Previously, when a workflow included a UI step as the final screen, followed by a workflow call step with a Failure dependency type, the Failure step was not executed if the UI step was closed in a dirty state. This behavior was unintended. The issue has been fixed so that the Failure step is now executed as expected when the UI step ends in a dirty state.
FIX: Mail service not processing emails without body
We resolved an issue where emails without a body would cause the NetStandardMailService to fail during processing. This fix ensures that emails can be sent without a body without causing errors.
FIX: Search input set as catch-all parameter
We fixed an issue where search inputs containing encoded slashes resulted in a 404 error. The client search function now correctly processes such inputs without issues.