Release Notes 2025.10

release notes
1

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.

2

Version 2025.10.1.4038

FIX: Architect shows incorrectly detected model errors

Resolved an issue in Origam Architect where all model files were incorrectly flagged as misplaced, displaying errors such as “should be in .origam”. This fix ensures that only genuinely misplaced files are reported, improving the accuracy of the model validation process.

3

Version 2025.10.2.4117

FIX: Processing of state machine work queue hooks

We fixed a bug where state machine–triggered work queue actions were not executed for work queues that had a specific Queue Processor configured. The issue occurred because the state machine event logic filtered queues using the Queue Processor setting, causing the automated creation of queue entries to be skipped. This is now corrected so that state machine hooks work regardless of the WorkQueueProcessor configuration.

FIX: Start process wasn’t reflecting timeout value

Fixed an issue where the OperatingSystemService StartProcess method ignored the configured timeout, causing launched processes to run indefinitely instead of respecting the specified timeout. The timeout setting is now properly applied so that processes started via StartProcess are terminated and handled (the workflow step fails) when the timeout expires.

FIX: Could not open Architect because of LibGit2Sharp version error

Fixed an issue in Origam Architect where opening a project failed with a load error for the LibGit2Sharp assembly, preventing the IDE from starting. The correct LibGit2Sharp library version is now included and referenced, so Architect can open projects without this error.

FIX: Correct language reference in localization script

Resolved a bug in the Root package deployment scripts where localization inserts referenced fixed Language primary key values, causing failures on instances that don’t share those exact keys. Deployment now uses dynamic language lookup instead of hard-coded IDs, ensuring scripts run successfully across environments with different language key sets.

FIX: Failed password verification caused an error

Fixed an issue where the /account/ResetPassword endpoint crashed with a NullReferenceException when the password failed validation. Previously a hard-coded minimum length was applied and the configured PasswordConfig settings were ignored, leading to a 500 error on invalid passwords. Password validation now respects the configured rules and no longer causes an application crash.

4

Version 2025.10.3.4153

FIX: Duplicate key error inserting OrigamTraceWorkflowStep

We fixed an issue where inserting trace workflow steps could fail with a primary key violation (duplicate key) and related foreign key conflict when tracing workflows via the user API. This fix improves workflow trace handling and prevents the HTTP 500 error.

FIX: Path.Combine was incorrectly used for model path

Resolved an issue in Architect 2025.10 where expanding a menu binding dropdown could fail with an “Illegal characters in path” error due to System.IO.Path.Combine being used to build model paths containing characters such as “<>”. The fix removes the incorrect use of Path.Combine for model paths and restores the ability to list menu items in the dropdown.

FIX: Changed slash to backslash in metadata files paths

Fixed an issue where forward slashes in metadata .origam workflow file paths were incorrectly replaced by backslashes, restoring consistent path separators.