These are the 95 updates to step in version 2025.1, sorted with newest version first:
This supersedes 2025.1-2025-08-18-12-11-15 and earlier versions.
As a result of a fix to correct a Smartsheet validation action issue, it will now be possible to communicate with a STEP server with protocol Transport Layer Security (TLS) 1.3 enabled via Smartsheets from Windows11. TLS 1.3 is not supported on Windows10.
This supersedes 2025.1-2025-08-15-16-43-45 and earlier versions.
Now, the Hide Equal functionality works correctly on the Multi Workspace Screen when applied to attribute values that do not exist in the approved workspace.
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.
This supersedes 2025.1-2025-08-13-14-17-50 and earlier versions.
Further increased timeout for GCOverheadSensor before the warning about slow execution will be logged - from 20 to 60 seconds.
Autopagination now deletes old document in batches to reduce the size of transactions when processing large numbers of documents.
This supersedes 2025.1-2025-08-13-09-48-53 and earlier versions.
The fix removes mojibake characters (i.e., gibberish text) from all table freeText cell values when a table that is loaded is bigger than the configured threshold (default: 70mb). To enable the fix, the following configuration property should be added to the sharedconfig.properties file: FixSpecific.ISSUE792751=true To configure the threshold then the following configuration property should be added: Table.MojibakeTriggerSizeMb=70
This supersedes 2025.1-2025-08-08-07-10-51 and earlier versions.
Fixed a problem where context-specific data container values were not exported correctly.
Improved logging for Activity data so that it will give better information to investigate possible errors.
Fixed an unexpected exception that occurred in the STEP Workbench when editing unique key values.
This supersedes 2025.1-2025-08-06-06-46-41 and earlier versions.
STEP Workbench: When using the Advanced Search panel and having a search resulting in a large result list, showing the result list could take unnecessarily long time in the workbench client. This is only a problem for the systems where the limit on the number of shown results has been increased to more than the default of 100. This has now been fixed.
This supersedes 2025.1-2025-08-05-11-52-21 and earlier versions.
Fixed an unexpected ConcurrentModification exception when purging assets from the Recycle Bin.
For more information on this fix, see issue-796457 and issue-796462.
This supersedes 2025.1-2025-08-01-12-04-10 and earlier versions.
A previous commit from a related ticket was reverted to restore the correct sorting order.
This supersedes 2025.1-2025-07-31-11-09-16 and earlier versions.
Fixed a problem in which the Log tab with attribute log lines with line breaks was unavailable in the STEP Workbench due to an unexpected exception.
This supersedes 2025.1-2025-07-29-10-26-44 and earlier versions.
It has been seen that the STEP background process (BGP) system stops scheduling new BGPs due to internal duplicates of values used for controlling the state of the BGP (running, waiting, succeeded,etc.). This fix makes the BGP system able to survive cases where LOVs used by BGPs have duplicates. For instance, the status attribute containing the state running, waiting, succeeded, etc. Also ensured specifically for the status attribute that creating duplicates is not possible anymore. This also includes removing any duplicates already created.
This supersedes 2025.1-2025-07-28-10-19-36 and earlier versions.
If a system was configured with the configuration property Calculated.TemplateRoot that was set to a directory that did not exist, an error would occur when editing a Calculated Attribute function. This has been fixed.
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).
This supersedes 2025.1-2025-07-24-06-26-27 and earlier versions.
A problem occurred when values could not be correctly identified as alphanumeric. In these instances, the system would fall back on simply comparing them as numeric, which caused all values to tie, which caused the system to then fall back on sorting by the ID column instead. This fix includes a check in the default case to see if the values are numeric. If not, a string comparison is performed instead.
This supersedes 2025.1-2025-07-21-10-35-51 and earlier versions.
An existing HOTFIX-8251 was backported to 2024.3. Fixed an unexpected exception related to navigating to an item after submitting it from the current state.
This supersedes 2025.1-2025-07-18-08-31-20 and earlier versions.
Fixed a problem that occurred with importing new publications when importing from Excel.
This supersedes 2025.1-2025-07-18-07-47-45 and earlier versions.
Now, Web UI configuration will reload Matching Algorithms cache every 30 minutes in addition to doing a Web UI configuration last edit date check to make sure that latest changes in the configuration are reflected.
This supersedes 2025.1-2025-07-17-12-19-30 and earlier versions.
Now, Web UI configuration will reload Matching Algorithms cache every 30 minutes in addition to doing a Web UI configuration last edit date check to make sure that latest changes in the configuration are reflected.
This supersedes 2025.1-2025-07-17-09-30-36 and earlier versions.
Fixed problem with business function results caching, which lead to missing export values that were related to business function mapping.
This supersedes 2025.1-2025-07-15-10-29-54 and earlier versions.
Increased time for which the GC Overhead Sensor can be executed before causing the warning about slow execution from 3 to 20 seconds - due to the slow GC logs reading.
Now, the Hide Equal functionality works correctly on the Multi Workspace Screen when applied to attribute values that do not exist in the approved workspace.
This supersedes 2025.1-2025-07-15-07-15-09 and earlier versions.
Now multi-value attribute values with units will not provoke unexpected exceptions in the Globally Configured Unfolding Data Container component in the Web UI.
This supersedes 2025.1-2025-07-14-11-57-19 and earlier versions.
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.
This supersedes 2025.1-2025-07-14-06-25-23 and earlier versions.
Fixed a NullPointerException occurring in the Globally Configured Multi Edit Data Container in the Web UI's design mode.
This supersedes 2025.1-2025-07-11-13-37-34 and earlier versions.
Now, an assignee's type (group or user) will be correctly determined by the Submit from Grid action when being opened in a Task List with status flag filtering.
This supersedes 2025.1-2025-07-11-11-22-41 and earlier versions.
Fixed a problem that, in very rare cases (race condition), could result in missing BLOB values (values longer than 4000 characters). The problem lied in that the Garbage Collector mistakenly could consider a BLOB value as garbage (and thus remove it) if it was written at the very same time as the garbage collector ran for that specific BLOB value.
This supersedes 2025.1-2025-07-11-09-50-37 and earlier versions.
Fixed an issue in Match and Merge Importer's new implementation where groups of records for matching and merging were duplicated, and because of that, the amount of records presented in the execution report's message was higher than amount of records provided in the import file.
This supersedes 2025.1-2025-07-11-09-18-36 and earlier versions.
Fixed a ClassCastException error thrown by the outbound integration endpoint (OIEP) Poller with GDSN Data Pool configured.
This supersedes 2025.1-2025-07-11-07-38-44 and earlier versions.
Now, Web UI configuration will reload Matching Algorithms cache every 30 minutes in addition to doing a Web UI configuration last edit date check to make sure that latest changes in the configuration are reflected.
This supersedes 2025.1-2025-07-10-17-23-50 and earlier versions.
Fixed a bug introduced in pipeline calculate-resolution introduced in a recent commit for a customer fix.
Fixed a NullPointerException that occurred during the Change Package impact analysis when handling the FunctionDependency tag of a local business rule of a workflow.
Fixed a NullPointer Exception (NPE) occurring when retrieving an asset from the recycle bin.
This supersedes 2025.1-2025-07-10-12-26-21 and earlier versions.
Fixed an unexpected exception in CharactersBetweenTransformation which was caused by an end character being placed before a start character.
Fixed problem so that changes in the JavaScript 'Applies If' condition are now saved when being edited via the 'Pen' icon in STEP Workbench.
This supersedes 2025.1-2025-07-09-12-32-26 and earlier versions.
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.
This supersedes 2025.1-2025-07-07-08-53-19 and earlier versions.
Added logging to expose possible error. Further investigation is ongoing.
This supersedes 2025.1-2025-07-04-16-43-56 and earlier versions.
In InDesign, if a product is placed using a product template frame that contains a “Require All” condition and anchors to other frames and the frame with the condition does not have any content when placed then none of the frames are placed. This has been fixed.
When using a “STEPGROUP AG” tag in an InDesign product template for which the product does not have values for any of its attributes in the specified attribute group, the text from the start STEPGROUP tag to the end STEPGROUP tag is deleted.
This supersedes 2025.1-2025-07-04-14-01-23 and earlier versions.
Fixed a problem that occurred in the mapDB implementation when mapDB files created by the exporter could be left in temporary Linux storage even after the process completed.
This supersedes 2025.1-2025-07-04-11-23-50 and earlier versions.
Fixed an issue in outbound integration endpoints (OIEPs) where product selection changes were not properly reflected in the endpoint's XML configuration. This fix ensures all product selections made in the UI are correctly persisted in the endpoint's configuration. In order to enable the fix, the following configuration property needs to be added and set to 'true': FixSpecific.ISSUE704765=true.
This supersedes 2025.1-2025-07-04-10-22-20 and earlier versions.
Fixed a problem that occurred when multi-valued Lists of Values (LOVs) with IDs were not saved correctly by the Globally Configured Unfolding Data Container component.
This supersedes 2025.1-2025-07-03-12-27-57 and earlier versions.
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.
This supersedes 2025.1-2025-06-30-14-44-52 and earlier versions.
Reduced memory usage by not showing data containers and headers for Globally Configured Multi Edit Data Containers in Web UI Design Mode.
This supersedes 2025.1-2025-06-30-08-58-04 and earlier versions.
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.
This supersedes 2025.1-2025-06-27-04-59-44 and earlier versions.
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.
This supersedes 2025.1-2025-06-26-13-05-31 and earlier versions.
Fix for solving side-effect in new version of com.stibo.util
This supersedes 2025.1-2025-06-26-06-58-25 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.
This supersedes 2025.1-2025-06-25-15-40-00 and earlier versions.
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.
This supersedes 2025.1-2025-06-25-13-31-49 and earlier versions.
Fixed a problem that occurred when records with a '0' match score were not merged even if they had a confirmed duplicate relation.
Added third-party library to Asset Push Sidecar to fix the problem that Asset Push stopped pushing assets.
This supersedes 2025.1-2025-06-24-06-19-20 and earlier versions.
Fixed renaming of files using the $autodetected-extension$ in a template.
This supersedes 2025.1-2025-06-23-12-10-52 and earlier versions.
Fixed a problem in Auto Classification Rules where the SkipIfRulesDoNotAllow property was not working as intended.
Fixed an unexpected exception on a Task List with Streaming, Sorting, and Filtering enabled.
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.
Added third-party library to Asset Push Sidecar to fix the problem that Asset Push stopped pushing assets.
This supersedes 2025.1-2025-06-23-11-30-21 and earlier versions.
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.
This supersedes 2025.1-2025-06-20-15-15-14 and earlier versions.
Fixed the incorrect status when images were not updated to upstream systems via Asset Push notify / sidecars.
Fixed renaming of files using the $autodetected-extension$ in a template.
This supersedes 2025.1-2025-06-20-11-43-11 and earlier versions.
We avoid the issue by limiting the number of cell indices for deep linking saved in the url
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.
This supersedes 2025.1-2025-06-19-14-46-24 and earlier versions.
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.
This supersedes 2025.1-2025-06-19-09-05-47 and earlier versions.
Fixed a memory leak caused by accumulating unused product URLs during the import.
This supersedes 2025.1-2025-06-18-14-51-21 and earlier versions.
Fixed renaming of files using the $autodetected-extension$ in a template.
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.
This supersedes 2025.1-2025-06-18-12-22-40 and earlier versions.
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.
This supersedes 2025.1-2025-06-17-15-07-29 and earlier versions.
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.
This supersedes 2025.1-2025-06-17-10-53-35 and earlier versions.
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 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.1-2025-06-12-18-03-20 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.
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, an LOV ID sorting order will be correctly respected in an Add Data Container popup on a Web UI Multi Edit Data Container component.
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.
This supersedes 2025.1-2025-06-11-12-43-07 and earlier versions.
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.
This supersedes 2025.1-2025-06-11-07-45-13 and earlier versions.
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.
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.1-2025-06-10-10-17-17 and earlier versions.
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.
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.
This supersedes 2025.1-2025-06-09-13-59-42 and earlier versions.
Returning LOV and multivalued attributes in REST API v2 now.
This supersedes 2025.1-2025-06-05-08-59-38 and earlier versions.
Now, the Web UI compressed component store size will be limited to avoid OutOfMemory problems.
This supersedes 2025.1-2025-06-04-09-37-54 and earlier versions.
Fixed a problem where empty inherited references were not shown in GraphQLv2 response.
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.
The issue solves a problem of empty node id and url while reindexing data.
This supersedes 2025.1-2025-06-03-11-06-57 and earlier versions.
Fixed unexpected error occurring when double clicking on a Workflow Pie Chart on a Web UI home page.
This supersedes 2025.1-2025-06-02-10-11-00 and earlier versions.
We have implemented a fix that ensures
Previously, customers encountered an 'Internal Application Error' when attempting to save Local Business Rules that were not linked to any workflows. With the recent update, it is now possible to edit and save changes to these Local Business Rules without any issues.
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.
Fixed unhandled exception when adding a new Auto Classification Rule to the table with applied filtering in STEP Workbench.
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.
In InDesign, if a product is placed using a product template frame that contains a “Require All” condition and anchors to other frames and the frame with the condition does not have any content when placed then none of the frames are placed. This has been fixed.
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).
This supersedes 2025.1-2025-05-28-10-03-49 and earlier versions.
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.
Added a config-dependent solution to make a guardrail protecting against large values more flexible.
Fixed a faulty sort comparator in Tree Navigator.
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.
Added log information to integration endpoints to enable troubleshooting of errors
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.
This supersedes 2025.1-2025-05-27-07-53-48 and earlier versions.
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 BMEcat export, based on ETIM 9, so that FVALUE DETAILS values are exported correctly.
This supersedes 2025.1-2025-05-27-07-04-34 and earlier versions.
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.
This supersedes 2025.1-2025-05-26-12-22-12 and earlier versions.
Improved logging when trying to retrieve a malformed SVG icon from the workbench.
This supersedes 2025.1-2025-05-23-18-32-57 and earlier versions.
To improve Asset Push functionality, Asset Push now runs on Java 21.
This supersedes 2025.1-2025-05-23-15-03-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.
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.
This supersedes 2025.1-2025-05-23-11-16-07 and earlier versions.
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.
This supersedes 2025.1-2025-05-19-14-07-34 and earlier versions.
It is now possible to enable OPTIONS preflight for HTTP.
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.
Fixed an unexpected exception and incorrect item count on a Web UI Task List with streaming sorting and filtering enabled, when a Task List was displaying a Total state of a workflow with parallel states, where items could appear in multiple states.
Empty assets were not migrated from Oracle to Cassandra. A workaround has been made to solve this problem.
Oracle Data Migration: Fixed the problem that empty asset content was not migrated.
This solution is a performance improvement for Bulk Updates, when using SQL to fetch the nodes in the collection being updated (currently not the case when using Cassandra). In most cases a query would be done for each node. Now, a query should only be done every 1000 nodes.
Fixed an UnsupportedOperationException error that was thrown when trying to change an LOV-based attribute validation via import without being in Single Update Mode (SUM) and the import file contained the unit links.
This supersedes 2025.1-2025-05-19-07-44-45 and earlier versions.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
Now, empty emails will not be sent via the Outbound Error Reporter when the corresponding BGP reports a warning about splitting export.
This supersedes 2025.1-2025-05-09-14-23-59 and earlier versions.
Fixed a problem that occurred when an invalid user-added typeahead suggestion on a Web UI Node Editor with business conditions caused an unexpected exception when resolving this condition.
Fixed a problem where a renamed asset would fail to export if the destination path did not exist.
Fixed an issue where searching for object types without valid data containers would trigger an unexpected error on Web UI Node Lists configured with Data Container Value headers.
This supersedes 2025.1-2025-05-06-17-31-28 and earlier versions.
Fixed a problem that occurred when a single-valued LOV without ID was not promoted to golden record via the Trusted Source Multi Context Value survivorship rule.
Now, a retry will work for all Socket exceptions in Loqate Cloud / Enhanced Loqate Cloud plugins instead of just Connection reset cases.
Added log information to integration endpoints to enable troubleshooting of errors
Fixed a problem that occurred when references were double-exporting in Excel and STEPXML.
A value- or name-validation error would previously cause an import in a new implementation of Match and Merge to stop.
Now, Multi Data Containers will be marked as different on Multi Revision screens in the Web UI if they indeed have different values.
Changed default values to true for config properties allowing Customer MDM customers to modify Deactivated attributes and Source Relations to avoid problems when migrating from older versions (where changing Deactivated attribute and Source Relations was allowed). This change applies to latest version available for on-premise customers on 2024.4.
In the eClass Advanced system, Multi Valued LOV attribute is now disabled from allowing users to select the same value more than once.
Resolved issue where data would appear duplicated in the web service response when Object Linking and Embedding (OLE) occurs, but would succeed when retried.
Selecting a new item for the reference input was causing the deselect event to also get triggered, most likely because of the typeahead logic that lies behind the component. With this change set, we can differentiate between a newly selected item and an actual deselection, therefore preventing this diselect event to get triggered when no needed.
To fix an issue emptying attributes in data containers following Match & Merge, a Survivorship business rule behavior change has been made. Now, empty values are allowed to be survived when manually setting an empty value when using Survivorship business rules. Now, the empty values are reflected in the survived record.
A Bulk Update to permanently delete a node through a business action was causing an exception when trying to access the title of the node for output logs (the node is no longer accessible as it had already been deleted). This change catches the exception and assigns a custom name "Unknown Node (detached or inaccessible)" for the output logs.
Due to several different dependencies between incoming data, a collection of records that must be processed together could cause the task to become too large for the underlying Oracle database. This has been corrected by doing intermediate commits instead of when the entire job is processed.
Fixed handling of Constant Mappings into Data Containers in the inbound Streaming Mapper, so multiple mappings do not overwrite each other.
A change in the filter implementation allows matching on value IDs when filtering on a hard LOV using such value IDs.
Now, an ampersand character in Web UI screen IDs will be automatically replaced with an underscore when creating / renaming the screen.
Fixed an exception in a Match and Merge importer new implementation that occurred when a new record with source information was created and then another record refers to it by the source information cross reference. Sometimes it failed when updating contributor data. This has been fixed now.
In advanced search in the workbench in a search for 'Data Containers,' an 'Instance Count' box is present. If a number with more than one digit is inserted in the 'Instance Count' box, then all digits are now also used in the search when In-Memory is used.
Created the temporary configuration property, FixSpecific.ISSUE768063. If the property is set to true, it will change the behavior for updates on connected sources, (e.g., when an update is done and the StepID is passed in the request). Normally, when in the connected source case, all sources are trusted equally; this is the regular behavior. When the FixSpecific.ISSUE768063 property is applied, all sources will not be treated equally. They can be ordered by importance, most important being the attributes that have the mostTrustedSource survivorship rule set up.
This supersedes 2025.1-2025-05-05-07-01-19 and earlier versions.
Fixed a multithreading problem, which caused getNumberOfUnreadEvents REST API v2 to lock concurrent threads if retrieving the number of events took very long.
This supersedes 2025.1-2025-05-01-14-24-03 and earlier versions.
When saving an invalid XML/JSON output template on integration endpoints, the mappings will get removed. Validation has been added that prevents the user from saving an invalid template. In order to enable HOTFIX-8312, the following configuration property needs to be added: FixSpecific.ISSUE757433=true
Improved the log tab for event processors in workbench. Now, log messages from Event Processor and event queue are sorted and deduplicated.
To correct an issue with invalid characters being added in one kind of attribute if a different kind of attribute is left empty, an adjustment has been made to disable the ability to add / edit for the relevant attribute type.
Fixed an issue with Asset Publisher where the Version Attribute Value was not updating with every publish event.
This supersedes 2025.1-2025-05-01-06-55-49 and earlier versions.
Improved error message for the 'Add Data Container' action when a user does not have privileges to add a data container of the given type.
Now, Global Navigation Panel with Direct Navigation in Web UI will not forcefully set the selection of a Direct Navigation's screen that will lead to problems with Advanced Search redirection.
Fixed a reloading error that occurred in the Compare view when filtering was applied.
Fixed the basket node count in STEP 2024.2.
Fixed an issue with LOV-based attributes within a Globally Configured Data Container using Unfolding View. The problem was that the LOV select field did not correctly get the readOnly state from the configuration. Instead, it used a default value when there were no LOV values selected.
An existing HOTFIX-8251 was backported to 2024.3. Fixed an unexpected exception related to navigating to an item after submitting it from the current state.
Fixed s setback, which caused an unexpected exception on a Web UI Node Editor with a Data Container popup component for read-only users.
Fixed validation for LOVs with IDs on a Web UI Node Editor Attribute Value component for LOV attribute with more than 5,000 values.
Fixed an unexpected exception shown for the Web UI Add Data Container popup when editing non-LOV multivalued attributes.
Introduced a customer-specific solution to disable display of the text "No values supplied" in otherwise empty values in the Table Header Data Container Value on the Web UI Node List.
Fixed an unexpected exception encountered when adding a custom style tag in the Web UI Rich Text Editor.
Now, filtering works correctly for the Table Header Business Function on Web UI Node Lists.
Fixed cross-context validation for the Globally Configured Multi Edit Data Container. The issue occurred when the user was unable to exit the edit mode when modifying an LOV attribute in the Globally Configured Multi Edit Data Container.
Fixed an Out Of Memory error that was thrown when downloading a Web UI asset as an attachment when its size in bytes was bigger than the maximum integer value.
Improved the 'no image' placeholder Thumbnail for the Table Display Mode Thumbnail Header on a Web UI Node List to look similar to Multi Edit Display Mode.
Now, the Hide Equal functionality works correctly on the Multi Workspace Screen when applied to attribute values that do not exist in the approved workspace.
Saving a page in Web UI with multiple changes could, in some cases, fail with an exception. This has been fixed.
This supersedes 2025.1-2025-04-30-07-34-59 and earlier versions.
To understand how Elasticsearch events are calculated and how much time it takes for re-indexing, a customer-specific solution was introduced to enable a domain-driven strategy for Elasticsearch publishing. An existing hotfix (HOTFIX-8245) was backported to 2024.2.
Now, a JWT cache security key will be invalidated to prevent situations in which one of the nodes in a STEP cluster has the old cached security key.
The fix is to allow the export of external DAM asset content (previously, the exports were failing with an unexpected exception).
Fixed an issue with split transformations in the exporter mapping. The problem was that the result value was empty when there was no delimiter in the value.
Fixed the BMEcat export result file, which should not contain ARTICLE_TO_CATALOGGROUP_MAP tag without corresponding ARTICLE tag.
Fixed a NullPointerException, which was thrown during the export of an empty LOV.
Fixed a problem where Bulk Update Configurations were not exported in STEPXML format.
Fixed a NullPointerException that occurred when editing import configurations in the workbench with multiple data containers and variable mapping.
To fix an issue with a NullPointerException error in the production environment, more logging was added to better detect the problem.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
Now, a guardrail will prevent users from setting a value larger than 1 million instead of the 100000 max, which caused an error during the large imports.
Fixed unexpected exception when downloading external asset with a URL longer than 100 characters via Asset Download Home bind in business rules.
When exporting data below a publication where the format is Publication Excel with section names that are language dependent, then the selected context (Advanced tab) is used to determine the names. The following configuration property needs to be added: FixSpecific.ISSUE769638=true
Improved logging for failed ES indexing BGP.
Security update for a library used in the core component
It is now possible to force delete object types linked to matching algorithms and/or get a better message, when not force deleting. Previously, when trying to delete, you would get an error message that was unclear.
General improvement to remove unused system code.
Now, data containers without an owner object will be skipped during export instead of failing the whole export.
Updated third-party libraries.
Updates a library used in server configuration
Fixed a problem that occurred when the validation base type of an imported attribute was lowercase, which caused an unexpected warning about Single-Update Mode (SUM), even though there were no changes in the imported attribute.
This supersedes 2025.1-2025-04-28-13-43-08 and earlier versions.
The proxy fields in the InDesign "Connect to DB..." dialog were incorrectly ignored when logging in via Single Sign-On (SSO). To correct the issue, support has been added for using a proxy when connecting to STEP from STEP Publisher using SSO.
Fixed an issue in which InDesign plugins crashed due to a NullPointerException error.
When exporting data below a publication where the format is Publication Excel with section names that are language dependent, then the selected context (Advanced tab) is used to determine the names. The following configuration property needs to be added: FixSpecific.ISSUE769638=true
To fix an issue in which data container attributes were case sensitive, data container searches on the Advanced Search screen will now be case insensitive by default, just like a Value search.
Updated the library used by the single sign-on component.
This supersedes 2025.1-2025-04-24-17-58-02 and earlier versions.
Implemented a security update for the system.
Security update for library used in the admin portal.
Fixing problem with messages being produced to a single partition
General improvement to remove unused system code.
The View button / functionality was not accessible when users first accessed multiple products due to a problem with custom views in the workbench. This has been fixed.
Fixed an unexpected exception occurring when reloading an Attribute Management screen after changing an LOV filter, if there is more than 100 nodes, which are using this attribute.
This supersedes 2025.1-2025-04-22-18-38-14 and earlier versions.
This supersedes 2025.1-2025-04-09-10-48-54 and earlier versions.
General security improvements have been implemented to enhance the overall security of our systems.
When the system setting 'DTPSettingsPrefixPublication' is enabled, then the name of an 'InDesign Document' objects/folders is prefixed with the name of the publication in the context for the oldest version that is created on the publication. The name of the 'InDesign Document' object is the same in all contexts.
This supersedes 2025.1-2025-04-08-15-15-35 and earlier versions.
There was an issue with retrieving information in regards to why the context deletion had failed in Workbench therefore making it difficult for the user to identify what was causing them problems. This change set remedies that issue by adequately communicating the reason for the failure to the user.
Introduced a possibility to set an SO timeout for FTP delivery to fix a customer-specific issue.
Implemented a change to how null object errors in STEP Workbench are handled when opening an attribute in System Setup and the source endpoint for the translation of that attribute has been deleted. In order to enable the HOTFIX-8201 the following configuration property needs to be added: FixSpecific.ISSUE.757899=true
To fix an issue in which attempts to access the workbench failed with an error, a performance improvement implemented in the STEP Workbench in the 2024.4 update was backported.
This supersedes 2025.1-2025-04-03-18-13-56 and earlier versions.
To fix an error in which the translation status did not update correctly, the translation status is now set to "Up-To-Date" if the translation went well and no new changes to the sources are present.
Overridden calculated attributes were not included in exports if "Include Calculated Attribute Values" was not selected. This has been fixed.
Due to improved functionality for replacement rules added in the STEP 2024.1 update, STEP XML imports using these tags suffered a performance drop. This fix tries to remedy some of that performance drop.
Fixed potential out-of-memory errors that occur when querying large lists of classification-product links, references, or nodes in NodeCollections. The query NodeCollection.queryNodes on Oracle allows JVM to GC nodes already returned by query (previously, already returned nodes were kept in a hard reference from within the DataNucleus query object). Also, calling queryReferences, queryReferencedBy, and queryClassificationProductLinks do not cache already returned objects by query (unless query size is less than a configurable size - default size is 10000 before going into query mode).
Fixed a problem that occurred when the "hostname" parameter was not restored correctly from the delivery configuration during SFTP Translation delivery.
Fixed an issue with Asset Publisher where the Version Attribute Value was not updating with every publish event.
Now, the old Elasticsearch reindexing processes will be correctly deleted automatically, allowing reindexing to start again.
Fixed a problem where datasheet PDF creation caused an error when using the "Approved" workspace.
Fixed a problem in which datasheet PDF creation caused an error when using the "Approved" workspace.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
An issue where the Instrument documentation and Elasticsearch were unavailable has been fixed.
Fixed a No Such Method error caused by a partial backport.
It is now possible to force delete object types linked to matching algorithms and/or get a better message, when not force deleting. Previously, when trying to delete, you would get an error message that was unclear.
This supersedes 2025.1-2025-04-01-17-32-23 and earlier versions.
In edge cases, the addition or deletion of data containers (only applied to those that are not unfolding), caused the Web UI to flicker and the list of data containers to be refreshed with unexpected items (e.g., you delete a data container, but it reappears on the list). This was due to a race condition happening in certain edge cases, and primarily when the system was very slow and the user was trying to interact with it. This change set accounts for that edge case by waiting for the previous action to be stored before the user can continue editing in order to ensure data is always in its latest state.
Fixed a problem that occurred when having a value of "OCT" for the month for a date-validated attribute value resulted in a validation error on the Web UI Node Editor screen in the Attribute Value component.
General security improvements have been implemented to enhance the overall security of our systems.
Now, Numeric text (excluding tags) validation base type attributes will be handled similar to Numeric Text attributes during the Smartsheet import.
Fixed a setback related to exiting edit mode on Multi Edit Display mode in the Web UI.
Fixed a problem in which an unexpected exception was thrown when the system evaluated business conditions for the Multi Edit Data Container. After an item configured with this component was submitted to the next state, the user was navigated out of the current screen. This has been fixed.
Fixed an issue related to long loading times in the Web UI by introducing a private configuration property (FixSpecific.ISSUE.765754) set to false by default. When set to true, an automatic checking process to ascertain whether an attribute was valid in previous revisions will be skipped on the Multi Revision screen in the Web UI to address the performance issue.
Fix for an issue that occurred where data was entered and saved in a data container table, but the table displayed as empty on subsequent logins. Now, Globally Configured Multi Edit Data Containers will show existing data containers when they become visible under the Grouping Option on the Web UI Node Editor screen.
Fixed an issue in which workflow objects were not displayed if the supplier user was also part of standard user groups. Added a new configuration property to ignore supplier roots.
Now, it is possible to change the default limit of tokens in GraphQLv2.
This supersedes 2025.1-2025-03-31-12-46-24 and earlier versions.
Resolved issue where data would appear duplicated in the web service response when Object Linking and Embedding (OLE) occurs, but would succeed when retried.
Fixed a NullPointerException in the Match and Merge Importer V2 that occurred when the imported file contained non-existent attributes.
Security update to fix potential vulnerability
Corrected the "FIX" part for three health checks: "Unrevised values should be revised", "Revised values should be unrevised," and "Edges with invalid revisability", so it does not fail with an Oracle error.
This supersedes 2025.1-2025-03-27-19-02-21 and earlier versions.
Implemented a security update for the system.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
General security improvements have been implemented to enhance the overall security of our systems.
Fixed a problem where Datasheet PDF creation in workbench caused an error when using the 'Approved' workspace.
Importing a publication that contained an asset could fail with a 'Data after ValueStack empty, should never happen' error. This has been fixed.
This supersedes 2025.1-2025-03-25-19-12-21 and earlier versions.
Now, queryUsedByAttributes used in JavaScript business rules will not return invisible technical attributes used by LFSC.
Fixed issue with vertical scaling in SaaS v2 environments.
Made a change so that we can make temporary config properties which can be removed again without STEP failing to start. If a config property starts with FixSpecific. and it is not defined in STEP, the application server will now simply warn instead of fail to start. This is to enable us to better support customers in the future without risking side-effects for other customers. This change is only internal and for future use, so it has no effect on any existing systems.
security update to tpl
Fixed a problem where the price list was ignored when performing an eCatalog export.
Implemented performance optimization for Cassandra-specific STEP instances related to purging revisions. The time required purge revisions was taking a long time checking, specifically if there were events for the revisions.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
Improved error message on a Web UI Advanced Search screen when a user without privileges to see the collection group root was trying to create collection underneath it.
To correct the null pointer exception issue, the Kafka Receiver plugin can now optionally skip null values from Kafka.
In an outbound integration endpoint (OIEP) using batching, if delivery failed causing a batch to be split and retried, the same events could get sent multiple times. This has been fixed.
Fixed a problem where the price list was ignored when performing an eCatalog export.
Implemented a change to how null object errors in STEP Workbench are handled when opening an attribute in System Setup and the source endpoint for the translation of that attribute has been deleted. In order to enable the HOTFIX-8201 the following configuration property needs to be added: FixSpecific.ISSUE.757899=true
Reports do not work when the internal node ID is larger than a 32-bit integer, which can be the case for STEP systems that have been in use for many years. This has now been corrected, so it is no longer a problem when internal node IDs exceed the 32-bit integer limit.
Fixed an issue in which workflow objects were not displayed if the supplier user was also part of standard user groups. Added a new configuration property to ignore supplier roots.
This supersedes 2025.1-2025-03-24-13-20-25 and earlier versions.
Now, LOV values on the List of Values Management screen in Web UI will be sorted in the same order as in workbench.
Made a change so that we can make temporary config properties which can be removed again without STEP failing to start. If a config property starts with FixSpecific. and it is not defined in STEP, the application server will now simply warn instead of fail to start. This is to enable us to better support customers in the future without risking side-effects for other customers. This change is only internal and for future use, so it has no effect on any existing systems.
This supersedes 2025.1-2025-03-21-13-17-01 and earlier versions.
To fix an issue related to case sensitivity, the Asset Importer's File Name matcher is now case-sensitive if it contains the corresponding regular expression.
Now, AND Object Type searches on Advanced Search screen will return valid results and will not behave as OR searches.
This supersedes 2025.1-2025-03-21-09-49-57 and earlier versions.
Corrected the "FIX" part for three health checks: "Unrevised values should be revised", "Revised values should be unrevised," and "Edges with invalid revisability", so it does not fail with an Oracle error.
General security improvements have been implemented to enhance the overall security of our systems.
This supersedes 2025.1-2025-03-20-17-52-59 and earlier versions.
Now, the Split Layout Panel (used on a Packaging screen) will not be resized when it is invisible, when a user clicks into different tabs of a Web UI Node Editor.
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.
The Multi Edit Display Mode Web UI component could not export references from the Approved Workspace. It has been fixed so now the Web UI component exports references from the Approved Workspace.
If a 'Connection reset' exception is thrown when connecting to Loqate Cloud, then the request is resent and up to 5 retries are made.
Now, item IDs with dashes will be correctly sorted on a Web UI Node List screen.
Now, a Multi Value Editor on the Multi Context screen will correctly save chosen values.
Now, inheritance indicators will be visible in a read-only Web UI References component on a Web UI Node Editor screen. Note that the indicators column will be empty if there are no indicators, and the 'Delete Reference' action will be unavailable due to privileges or read-only settings.
This supersedes 2025.1-2025-03-18-11-01-44 and earlier versions.
When the triggering workspace of an event processor plugin configuration is changed, the triggering workspace is now updated immediately, instead of the next time an event is processed.
Fixed an incorrect time conversion occurring in state logs when servers were not running in UTC.
This supersedes 2025.1-2025-03-14-12-33-29 and earlier versions.
Fixed an issue with the incorrect parsing of assets in the PDF format.
Fixed an issue that caused the faulty parsing of PDF files.
When purging from a node collection, the system now splits the query into several smaller chunks in order to avoid having a snapshot open too long. A snapshot open too long can cause the application server to run out of memory because the vacuum cleaner cannot do its job.
To fix an issue resulting in STEP becoming unavailable, guardrails were implemented that prevent users from creating too many revisions for a node, too many multi values, or values that are too large.
A problem occurred when product data was getting updated even after the product was rejected by the business condition. To correct the issue, a previous fix which introduced unnecessary side effects was reverted.
To address issues surrounding ETIM and BMEcat, a fix has been implemented that allows STEP to export empty values converted to text using transformations, and not export not-converted empty values using BMECat2005 exporter. This requires a config property to be set as follows: ExportManager.BMECat2005.ExportValidAndAbsent=true
This fix only applies to STEP with InMemory. This fix corrects the scenario in which an object with incoming references is deleted. All the incoming references should be deleted as well (or marked for deletion), however, prior to this commit the system would not delete incoming references that were created in the same transaction as the deletion of the target object. This rare case has now been fixed.
Added DAM variant of pipelines for web-proof-small and web-proof-medium.
Now, invalid characters from an endpoint name will be escaped when creating temporary files for export.
Now additional privileges are not required to export manual Excel translationsfor LOVs with IDs.
Fixed an EmptyStackException during the import replay and added logging for further investigation if the issue ever recurs.
Fixed a NullPointerException occurring in the Generic XML import.
Fixed retrieving PDF XMP metadata properties acc. to format of file: application/pdf after uploading Asset in workbench.
Fixed a problem with hot deployment of customer-developed components causing background process executor to be shut down.
This supersedes 2025.1-2025-03-11-14-32-15 and earlier versions.
A Task List page was taking too long to load. Now, data container values on Web UI Node Lists will load when needed instead of loading automatically when a Table Header Value component is configured on the screen.