These are the 15 updates to saas in version 2025.2, sorted with newest version first:
This supersedes 2025.2-2025-06-19-15-23-50 and earlier versions.
The problem with sorting was related to a pagination problem on some node fields, like f.e. Approval Status. They do not have lower case representation indexed in Elasticsearch, which led to a pagination problems as the system tried to use it. My change does not require any reindexing. I am just checking if a sorting field has lower case representation. If so, the search after (pagination) mechanism take lower case value into account. Otherwise, it uses the original value.
This supersedes 2025.2-2025-06-18-14-30-35 and earlier versions.
An error occurred because a translation partner expected specific translation file-naming conventions in the translation file they received from the customer. The naming discrepancies caused translation files to be rejected in a specific use case. To fix the issue, the translation file name now defaults to the expected naming convention (translation.xml) should it not find translation files following the translation-BGP_(\\d+)-(.*).xml file-naming pattern.
Addresses a specific edge case encountered during Asynchronous Translation on a customer system, where two translation files were generated—one of which was empty. This resulted in a premature end of file error when importing the response from Lionbridge. The fix introduces an additional sanitization step that filters out empty files from the list prior to processing. This covers files that are 'Truly empty' meaning that they have a size of 0Kb, 'Effectively empty' files still pass as they do have a root defined within.
Under certain system configurations, creation of InDesign packages could result in missing files. The Create InDesign Package background process can now be configured to always use a shared directory.
General security improvements have been implemented to enhance the overall security of our systems.
To fix an issue that occurred when creating assets without content using the Asset Importer, optional skipping of System Properties for empty assets has been added.
Improved handling of an edge case when customer-defined behavior conflicts with recommended practices: https://doc.stibosystems.com/doc/version/latest/web/content/busrules/conditions/business_condition_evaluate_javascript.html 'Although it is technically possible to write business conditions to change data, doing so can result in unpredictable errors and should therefore not be attempted.' This specific issue was observed in the Datasheet OIEP when attempting to revive a deleted asset. In this case, a customer-defined business rule triggered during the revival process and attempted to modify the asset, resulting in an OptimisticLockException. This update improves resilience by gracefully catching the exception, allowing the process to continue without termination.
Decreased 'Severe' severity for log messages related to extension API errors to 'Finest.'
Fixed the issue, which was not updated during ECLASS import.
This supersedes 2025.2-2025-06-16-13-48-57 and earlier versions.
Fixed the incorrect status when images were not updated to upstream systems via Asset Push notify / sidecars.
An error occurred because a translation partner expected specific translation file-naming conventions in the translation file they received from the customer. The naming discrepancies caused translation files to be rejected in a specific use case. To fix the issue, the translation file name now defaults to the expected naming convention (translation.xml) should it not find translation files following the translation-BGP_(\\d+)-(.*).xml file-naming pattern.
Addresses a specific edge case encountered during Asynchronous Translation on a customer system, where two translation files were generated—one of which was empty. This resulted in a premature end of file error when importing the response from Lionbridge. The fix introduces an additional sanitization step that filters out empty files from the list prior to processing. This covers files that are 'Truly empty' meaning that they have a size of 0Kb, 'Effectively empty' files still pass as they do have a root defined within.
Now, an LOV ID sorting order will be correctly respected in an Add Data Container popup on a Web UI Multi Edit Data Container component.
Fixed a faulty sort comparator in Tree Navigator.
Fixed an unexpected validation exception on a Web UI Node Editor screen caused by evaluation of a Business Condition for LOV attributes, where one value had the same ID as another LOV value's value.
Now, an OK button will be disabled on the Add Data Container Popup, which contains only LOV-mandatory attributes, if the attribute values are not provided by user.
Fixed unexpected error occurring when double clicking on a Workflow Pie Chart on a Web UI home page.
General security improvements have been implemented to enhance the overall security of our systems.
Now, the Web UI compressed component store size will be limited to avoid OutOfMemory problems.
Fixed a problem that occurred when the Web UI Node List did not clean the selected item after it was deleted or removed from the list as a result of a Run Business Action execution.
This supersedes 2025.2-2025-06-12-17-52-29 and earlier versions.
Improved performance of list value generator.
Fixed a problem in Auto Classification Rules where the SkipIfRulesDoNotAllow property was not working as intended.
General security improvements have been implemented to enhance the overall security of our systems.
This supersedes 2025.2-2025-06-10-11-54-12 and earlier versions.
When Match and Merge Importer uses anew implementation and there is a Standardized Business Action configured that adds or removes a reference type on an incoming node, such changes were not reflected in the result record. Now, this is fixed and changes made through a Standardized Business Action are visible on the result record.
Fix for upgrade library in component Blob storage to final version.
Fix for upgrade library in Blob storage component to latest version.
Fixed an issue in the Match and Merge Importer V2 implementation where importing the same entity twice resulted in default source information being added after the second import attempt. Now, the importer correctly preserves or updates source information without adding defaults on repeated imports.
General security improvements have been implemented to enhance the overall security of our systems.
Now, an HTML function Web UI component will not be displayed in a design mode in order to allow users to correct it if it causes an infinite reload.
Now, an Object Type Search descriptor in the Web UI will automatically transform an 'AND' object type search into an 'OR' object type search (as one node cannot have multiple object types).
This supersedes 2025.2-2025-06-04-12-01-23 and earlier versions.
When a user first logs into the workbench after a STEP system has been upgraded, a dialog is presented that offers to open the update notes for the new release (2025.2). This update notes link was broken and is now fixed.
Improved performance of list value generator.
Now, on a Web UI Multi Context Edit screen, when updating a cell, another cell will not be updated when clicking on another cell to exit the edit mode.
Information published in 2025.2 documentation.
Fixed a problem where empty inherited references were not shown in GraphQLv2 response.
Fix for upgrade library in InMemory component to latest version.
Fixed unexpected error occurring when double clicking on a Workflow Pie Chart on a Web UI home page.
Improved the Log tab for Event Processors in workbench: Now, log messages from Event Processors and the event queue are sorted and deduplicated. Log messages for all nodes will be sorted in workbench.
Backport of ISSUE-93079
General security improvements have been implemented to enhance the overall security of our systems.
General security improvements have been implemented to enhance the overall security of our systems.
This supersedes 2025.2-2025-06-02-18-51-44 and earlier versions.
General security improvements have been implemented to enhance the overall security of our systems.
Added a config-dependent solution to make a guardrail protecting against large values more flexible.
Fixed mapping problem occurring when mapping a variable with a constant data source, and then choosing a Data Container mapping for this variable, in the import wizard in STEP Workbench.
Added log information to integration endpoints to enable troubleshooting of errors
Fixed an IllegalStateException error that occurred when using Outbound Integration Endpoints (OIEPs) with the aspect 'File named by asset ID' or 'File named by asset Name' in the output template mapping.
Empty assets were not migrated from Oracle to Cassandra. A workaround has been made to solve this problem.
Fixed an issue that occurred when users received an unexpected error stating the external XSLT service had not processed the task yet and had ended the attempt. To address the issue, a private config property was introduced that increases the waiting time of the external XSLT microservice, which is set by default to 2500 milliseconds instead of hard-coded at the 2500 limit. This property cannot be larger than 10000 (10 seconds).
Oracle Data Migration: Fixed the problem that empty asset content was not migrated.
Fixed a problem where PDF metadata could become mixed up or corrupted when importing multiple files at the same time. This fix ensures that each file's information remains intact even when the system processes several PDFs simultaneously.
When a Photoshop EPS file with a large physical dimension specified in the bounding box was converted, the system crashed. This is now solved.
When a user first logs into the workbench after a STEP system has been upgraded, a dialog is presented that offers to open the update notes for the new release (2025.2). This update notes link was broken and is now fixed.
Improved logging for low-memory detector when using OneQueue BGP scheduler was added after an investigation of background processes not starting due to heap usage.
Fixed a problem when exporting the product parent with an empty URL selection when exporting leaf products ended up exporting only the parent and excluding the product children.
Fixed a problem with missing 8BIM profiles when "Keep Profiles" was set in Image Conversion Configuration.
Excessive caching could cause STEP to crash due to running out of memory. It is now possible to set a limit on the number of objects that are cached.
The OrphanDataContainers health-check had an error in its fix code that could cause a severe data inconsistency in STEP if the fix mechanism of that health-check is used. This has been fixed.
General security improvements have been implemented to enhance the overall security of our systems.
Improvements to new feature in 2025.2 with having BGP files in Blob Storage.
Fixed an issue that caused the average processing time of Approve Recycle Bin jobs to be more than 40 minutes if even one unapproved object was in the Recycle Bin. To fix the issue, a new health check was added and the node in recycle-bin missing a front revision was revised.
Suppressed unnecessary logging from OIEP Business Processor, which could have caused the out-of-memory (OOM) problem.
Now, the data container key will use a default unit if it was not specified by the "withAttributeValue" JavaScript Business Rule API, which will make sure that a new data container is not created if there is already a data container object with the same attribute value and default unit.
The issue solves a problem of empty node id and url while reindexing data.
This supersedes 2025.2-2025-05-28-19-58-16 and earlier versions.
To improve Asset Push functionality, Asset Push now runs on Java 21.
We have implemented a fix that ensures
Fixed unhandled exception when adding a new Auto Classification Rule to the table with applied filtering in STEP Workbench.
Improvements to new feature in 2025.2 with having BGP files in Blob Storage.
General security improvements have been implemented to enhance the overall security of our systems.
The issue solves a problem of empty node id and url while reindexing data.
This supersedes 2025.2-2025-05-26-06-27-16 and earlier versions.
Implemented a change to the Inbound Business Rule Message processor ensuring that business rules marked as "run as privileged" will run as such.
General security improvements have been implemented to enhance the overall security of our systems.
Fixed a problem occurring when adding a data container on a Web UI Node Editor via the Globally Configured Multi Edit Data Container component caused an 'Unsaved changes...' popup to appear when trying to submit a current item via Submit Action.
General security improvements have been implemented to enhance the overall security of our systems.
Fixed a problem when users with restricted privileges coud not access a Web UI if they did not have access to Web UI logo attributes.
Improved Web UI Pie Chart legend styling so that it now wraps to the next line instead of shifting and overlapping the chart when the legend values are too long.
Improved the Log tab for Event Processors in workbench: Now, log messages from Event Processors and the event queue are sorted and deduplicated. Log messages for all nodes will be sorted in workbench.
Fixed a problem where it was possible to save a data container without a key value on a Web UI Node Editor via the Globally Configured Data Container component.
General security improvements have been implemented to enhance the overall security of our systems.
General security improvements have been implemented to enhance the overall security of our systems.
This supersedes 2025.2-2025-05-23-14-56-37 and earlier versions.
Added extra check when matching users by key value.
This supersedes 2025.2-2025-05-22-11-39-33 and earlier versions.
Implemented a change to the Inbound Business Rule Message processor ensuring that business rules marked as "run as privileged" will run as such.