These are the 21 updates to step in version 2025.1, sorted with newest version first:
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.
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.
Adding a data container on a Web UI Node Editor via a Globally Configured Multi Edit Data Container component caused an "Unsaved changes..." popup to appear when trying to submit a current item via Submit Action with Workflow Navigation Handler configured. This is now fixed.
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-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.