The 2025.5 release introduces two new features, eight fixes, and one reverted fix.
FEATURE: [Database Structure Documentation]
This brand-new feature, located in a new package named Documentation, provides a read-only screen with basic documentation of database table fields, displaying the following attributes:
- Caption
- Name
- AllowNulls
- DataType
- DataLength
- Entity name
- DefaultValue
- IsPrimaryKey
- ForeignKeyEntity
- ForeignKeyFiled
- Documentation fields
To activate this feature, you need to add the Documentation package to your project. After that, you will find the Documentation screen in the client application’s main menu under Settings. More on this feature you find in this article.
FEATURE: XSLT function to convert JTSK polygon to WGS polygon
A new XSLT function PolygonFromJtsk has been introduced to support the transformation of polygon data from the JTSK coordinate system (used in Czech geospatial data) to the WGS-84 coordinate system, which is compatible with the SQL Server geography data type.
This function enables seamless processing of geospatial XML data received from external services, allowing polygons defined in JTSK format (e.g., POLYGON ((-740614.4101 -1030989.305, ...))) to be directly converted and stored in geography columns.
The transformation is handled internally by the Origam.Geo library, eliminating the need for custom transformation code or external services.
FIX: Workflow UI task was not working in ForEach block
Resolved an issue where UI steps within a ForEach loop were not displayed to the user, causing the workflow to proceed without awaiting user input. This fix ensures that UI steps are presented during each iteration, and the workflow correctly waits for user interaction unless the AutoNext setting is enabled.
FIX: PG Deployment Script Generator ends with SQL error
A bug in the SQL syntax, which caused an error when opening the Deployment Script Generator, has been fixed.
FIX: Passing array argument to modelled API caused an error
Passing an array of GUIDs as an input parameter to a Data API Page caused an error during XSLT transformation. The system attempted to convert the array to a string, resulting in an exception. Now the system doesn’t throw an exception but returns a message “Array cannot be converted to string.” as a content of converted value.
FIX: Table OrigamIdentityGrant was never cleaned up
The OrigamIdentityGrant table, which stores authentication tokens, was not automatically cleaned up, leading to the accumulation of expired entries. This has been resolved by introducing a cleanup procedure that removes expired tokens from the table during server startup.
FIX: UpdateObject was failing for rows with integer Id
Previously, updating entities with non-GUID primary keys (e.g., integers) resulted in errors during the UpdateData API call because the system attempted to convert integer IDs to GUIDs. This issue has been fixed — entities with non-GUID primary keys can now be updated correctly.
FIX: Exponential Retry Base could not be edited
For Work Queues, an issue was fixed where the Exponential Retry Base field became uneditable after switching to a Linear Retry policy. This prevented users from saving changes to the retry policy settings. The fix removed unnecessary field dependencies, allowing both retry strategies to be configured independently.