These are the 12 updates to step in version 2025.2, sorted with newest version first:
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.
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.