These are the 24 updates to step in version 2025.2, sorted with newest version first:
This supersedes 2025.2-2025-06-30-13-46-35 and earlier versions.
Fixed a bug introduced in pipeline calculate-resolution introduced in a recent commit for a customer fix.
Dual visible soft values in the health check (Softvalues for Dual Visibility) also works when the values are stored under edgeid instead of nodeid.
Assets used on multiple pages could not be purged from the Recycle Bin. This has been fixed.
Now the import preview will be able to read more than 1000 characters from the mapped column cell, which will fix the incorrect exceptions about tag validation.
Fixed a problem in which attributes without values or names were being exported in BMEcat 1.2 exports. To address the issue, a new configuration property has been introduced that, when enabled, does not add article feature elements when feature values or names are empty.
After upgrading to STEP 2025.2, starting BGPs could produce some severe log entries in step.0.log (especially when starting Event Processor BGPs) that are not really severe. These severe log entries have now been removed.
When exporting in generic JSON format, nested references are now correctly handled.
The HAProxy based loadbalancer is used for on-prem STEP systems, including development systems, so it needs to support the multitenant Instrument server. SaaS systems implement this support via the Kubernetes Ingress, which sits in front of the STEP app server and is not related to this change.
To fix an issue with a failing OIEP (outbound integration endpoint), a Rhino-xml third-party library was added to re-enable E4X (ECMAScript for XML) XML API in JavaScript.
Added third-party library to Asset Push Sidecar to fix the problem that Asset Push stopped pushing assets.
This supersedes 2025.2-2025-06-30-13-23-40 and earlier versions.
When running the Asset Importer in an IIEP, load the Asset Importer Configration according to the context configured on the endpoint, rather than default context. This makes it so that mapped attributes will get mapped against LOV values in the correct context.
Fixed a problem that occurred when records with a '0' match score were not merged even if they had a confirmed duplicate relation.
This supersedes 2025.2-2025-06-27-04-12-50 and earlier versions.
Returning LOV and multivalued attributes in REST API v2 now.
To fix an error that prevented products from being saved, a property was introduced that allows multi-value duplicates in the Web UI Node Editor. The property defaults to false but when toggled will introduce the desired behavior.
Introduced a configuration property that is set to false by default. When the property is set to true, the data profiling MapDB files will be cleaned up using the system GC on both Windows and Linux systems. Previously this approach was used only on Windows.
Under certain system configurations, the user-applied sorting of products in a Print on Demand publication was incorrectly ignored in the resulting pagination. This has been fixed.
Improved the error message for when you make multiple concurrent uploads of the same file to the same integration endpoint.
{code:title=before}
Operation failed as an exclusive lock could not be obtained for endpoint ID '
To fix an environment outage, the amount of undo / redo operations on a Mass Creation Screen in the Web UI will be reduced to 100 in order to save server memory.
Added third-party library to Asset Push Sidecar to fix the problem that Asset Push stopped pushing assets.
This supersedes 2025.2-2025-06-25-16-27-38 and earlier versions.
Fix for solving side-effect in new version of com.stibo.util
This supersedes 2025.2-2025-06-20-15-39-39 and earlier versions.
Fixed renaming of files using the $autodetected-extension$ in a template.
Added third-party library to Asset Push Sidecar to fix the problem that Asset Push stopped pushing assets.
This supersedes 2025.2-2025-06-19-15-01-32 and earlier versions.
Added gamma correction for 32-bit TIFF images to make these images look similar to other image viewers when viewed from the workbench image viewer.
Now, a healthcheck 'History entries pointing to non existing previous versions' will not hold the epoch lock, preventing LFSC processes from starting.
Some File-Not-Found errors could occur during Hotfolder handling and copying of files when under higher load, thus stopping the endpoint. This file handling has been made more robust, which should improve this problem. And additional logging has been added in order to better determine where the problem is, if it still occurs.
Fixed renaming of files using the $autodetected-extension$ in a template.
Fixed an unexpected exception on a Task List with Streaming, Sorting, and Filtering enabled.
To fix an issue that occurred where asset content was missing from asset objects, logging has been added in order to follow the progress of the health check for missing BLOBs.
Added detailed logging at level FINEST when node is not found in workspace during export.
Customers using a multi-server cluster without In-Memory use the Level 2 cache. And, the communication between those caches was accidentally restricted, which could cause the communication to fail. This causes optimistic lock verification errors that seem to be at random places. This has been fixed so that STEP does not impose such restriction itself, but leaves imposing the correct network restrictions to the network setup.
Fixed an issue where both imports and change package installs were unjustifiably failing when they included a link type which added an attribute group, in cases where the link type had data containers as a valid source.
Fixed problem, when existing files were not overwritten completely by new SFTP delivery plugin - instead the data was written inside those files. Now the existing files will be completely overwritten by SFTP delivery plugins.
We avoid the issue by limiting the number of cell indices for deep linking saved in the url
Updated dependency versions for libraries used by XSLT local transformation.
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 a memory leak caused by accumulating unused product URLs during the import.
Fixed problem, when depending LOV with similar ID on one LOV value with Value from another LOV value was causing invalid validation error in WebUI Node Editor screen when performing LOV cross validation business condition.
Approving object that is already fully approved now does nothing. Previously it could do an update in the revision of the object which could cause optimistic lock exception if doing this currently.
We fixed the way character tags are parsed in the case of multi-valued Lists of Values (LOVs) where values also contain other tags.
HOTFIX-8332: The $autodetected-extension$ filename macro now also works for Office documents. HOTFIX-8333: Custom image conversions can now be used to generate thumbnails of Office documents.
Fixed an Import Manager mapping problem when using an Intermediate Variable with a multi-value Constant to map into a Data Container where the value was not separated correctly from the multi-value Constant.
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.
Using Attribute Group Attributes data selector in a table, if "Exclude if empty" was selected and a child product was overriding the sort value with an empty value, the empty value on the child was incorrectly being ignored and the parent value would be used instead. This resulted in values appearing in the table when they should have been excluded.
The loadbalancer frontend needs to be able to understand the shape of the STEP cluster, but when new server types are created, the frontend does not understand those. This is a change to simply ignore new server types and rely on the already known types.
This supersedes 2025.2-2025-06-19-14-45-28 and earlier versions.
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.
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.
This supersedes 2025.2-2025-06-18-13-33-00 and earlier versions.
General security improvements have been implemented to enhance the overall security of our systems.
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.'
This supersedes 2025.2-2025-06-16-13-47-11 and earlier versions.
Fixed the incorrect status when images were not updated to upstream systems via Asset Push notify / sidecars.
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.
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-48-42 and earlier versions.
Fixed a problem in Auto Classification Rules where the SkipIfRulesDoNotAllow property was not working as intended.
This supersedes 2025.2-2025-06-10-11-52-33 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.
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-00-13 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.
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.
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.
This supersedes 2025.2-2025-06-02-18-27-37 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.
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.
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-27-17-30-25 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.
This supersedes 2025.2-2025-05-27-16-58-34 and earlier versions.
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.
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.
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.
This supersedes 2025.2-2025-05-26-05-46-37 and earlier versions.
General security improvements have been implemented to enhance the overall security of our systems.
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.
General security improvements have been implemented to enhance the overall security of our systems.
This supersedes 2025.2-2025-05-22-06-27-34 and earlier versions.
Webservice examples updated in documentation.
Updated documentation for Smartsheets classification inheritance. No code changes were made.
Kafka documentation was updated and provided to the customer. It will be published with the 2025.2 update.
Channel IDs from PDX that are longer than 100 characters are now hashed using UUID.nameUUIDFromBytes(...). The resulting 36-character ID is stored in the PDX Channels LOV. Example: id=f2c8c1a0-6c3e-3b3e-8a7e-4f5c8e4f6f3e, value={"name":"Skin Care", "parentChannelID":"Arts_PROD_Sample_Channel-KBduCjzT"} The original full Channel ID is preserved in the PDS Status Data Container.
The REST Direct Receiver documentation was updated to indicate that the receiver must specify the fileName.
Attribute Value Group Component documentation was reworked to clarify that in merged display mode, the attributes are displayed in alphabetic ascending order. Manual sorting order is not respected. This is standard and correct behavior.
The prerequisites for the Hotfolder Receiver Using File Sequence topic were updated. The documentation will go out with the 2025.2 update.
The customer found that if the tag:
Updated the Deduplicate mode description in the 'EP - Event Processor Tab' section for technical accuracy.
The Individual Customer topic found within the Customer & Supplier MDM Solution Implementation Guidelines solution enablement documentation was updated to reflect the correct REST example.
Information published in 2025.2 documentation.
The image for the Audit Message Framework Functionality Overview in online help was updated to correctly reflect current functionality.
More details to be provided as needed.
Updated incorrect code (line 13) available for generating product descriptions in the Azure OpenAI Integration topic within the Artificial Intelligence documentation.
Updates to shared config properties have been made and are ongoing to remove on-premises references and enforce SaaS-based directions. Updates will go out with the 2025.2 documentation.