These are the 62 updates to saas in version 2023.4, sorted with newest version first:
This supersedes 2023.4-2025-03-27-10-21-10 and earlier versions.
Fixed an issue with Asset Publisher where the Version Attribute Value was not updating with every publish event.
This supersedes 2023.4-2025-03-20-09-32-40 and earlier versions.
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 2023.4-2025-03-18-19-50-34 and earlier versions.
Fixed an issue with LOV export that would mix up values from different contexts when executing multiple exports in sequence.
This supersedes 2023.4-2025-03-11-14-08-13 and earlier versions.
Fixed an issue where the UI Product Editor may sometimes remain in a loading state. This was due to a security mechanism from GraphQL that stops the query should it be extremely large in size (exceeding the allowed amount of grammar tokens for the request). The change set accounts for this edge case and wires the request appropriately so that GraphQL is not overwhelmed.
Fixed an EmptyStackException during the import replay and added logging for further investigation if the issue ever recurs.
This supersedes 2023.4-2025-02-27-11-41-26 and earlier versions.
Improved Workbench bootstrap performance.
This supersedes 2023.4-2025-02-26-09-23-58 and earlier versions.
Changed check to avoid null pointer exception in webui when using the NodeList component. It's a fix for a specific problem, but it improves the overall stability of the NodeList component.
When running on Cassandra, validating a Smartsheet that creates both parent and child nodes could fail if a business condition took too long to run. Now, a business condition may run six (6) times as long before causing an error.
Performance improvement was made related to the method of counting nodes recursively in a hierarchy. This is, for example, used in asset migration.
This supersedes 2023.4-2025-02-25-11-58-02 and earlier versions.
Added logging to facilitate troubleshooting for GDSN publisher.
This supersedes 2023.4-2025-02-12-10-29-32 and earlier versions.
Performance improvement was made related to the method of counting nodes recursively in a hierarchy. This is, for example, used in asset migration.
This supersedes 2023.4-2025-02-11-10-38-27 and earlier versions.
Now, sub menus are aligned correctly in the Menu Group component on a Web UI Node List so that they will not fall down below the screen.
This supersedes 2023.4-2025-01-30-11-21-06 and earlier versions.
Fixed a problem occurring when the Hide Equal button on a Compare Records screen in Web UI was not hiding read only and non-read only date empty date values because of the date placeholder on a non-read only cell.
This supersedes 2023.4-2025-01-28-07-30-13 and earlier versions.
Fixed a problem occurring when an unexpected exception was thrown in STEP Workbench during the export when accessing a node, which was a target of a data container reference, invisible in a current context / workspace.
This supersedes 2023.4-2025-01-22-13-52-26 and earlier versions.
Fixed a problem where the STEPXML export with Flatten Hierarchy enabled sometimes did not cleanup temp files generated by hierarchy flattening, even after BGP completion.
This supersedes 2023.4-2025-01-20-11-14-21 and earlier versions.
Fixed the issue with accessing REST API V2 which happened when LDAP is used for STEP authentication and when a user tries to create a REST call is impersonated (e.g., by using an external component).
This supersedes 2023.4-2025-01-18-17-56-01 and earlier versions.
If you had an outstanding translation for an attribute for a language, which you deleted, you would get an error when trying to open the status tab for that attribute in the STEP Workbench. This has been fixed.
Fixed a bug that in certain circumstances could produce a NullPointerException. This could happen for long-running operations where hard-evicts had been performed.
This supersedes 2023.4-2025-01-14-09-55-41 and earlier versions.
Hotfix HOTFIX-7973 doesn't have an approved description, yet. This is related to ISSUE-695212, ISSUE-698944, ISSUE-751881.
This supersedes 2023.4-2025-01-09-08-45-44 and earlier versions.
Now, on the Web UI's Advanced Search screen, limits on filtering will be the same as those applied to the entire Advanced Search screen to prevent Out Of Memory issues. Previously, Advanced Search filters were not limited at all and this could lead to extensive memory consumption for huge searches.
This supersedes 2023.4-2024-12-13-14-43-43 and earlier versions.
Fixed unexpected error when adding a Match Score Updating Algorithms Representation to Web UI Main Area's global representations.
This supersedes 2023.4-2024-12-12-16-39-03 and earlier versions.
Hotfix HOTFIX-7986 doesn't have an approved description, yet. This is related to RDPORT-18116: Configuration LowMemoryDetector.HeapDumpDirectory : backporting fix.
Fixed a problem occurring when saving single LOV values with an ID via the Reference Metadata Table Header caused a random value to be saved instead of the one the user picked on a Web UI Node List.
This supersedes 2023.4-2024-12-11-12-26-38 and earlier versions.
This supersedes 2023.4-2024-12-10-10-17-01 and earlier versions.
This supersedes 2023.4-2024-12-06-11-30-27 and earlier versions.
The ScPL file, which is included in the JAR file for sidecars, will no longer contain properties that contain the string “secret” (with upper / lower characters).
This supersedes 2023.4-2024-12-06-07-49-33 and earlier versions.
If certain components are installed on a system and spot --upgrade was asked to plan an upgrade that included those components, then it would come up with an upgrade that was not actually possible. The problem was that the requirement for a different Java Runtime was not communicated via the dependency data that spot --upgrade uses to plan upgrades. This has now been rectified by making SPOT create the needed information for the software already on the system and by creating it for the available software, too.
Three fixes have been made to address issues with health checks: One, the Global Schema Change Log was being spammed with info about user settings being deleted. This information has no value as user settings are created and deleted all the time in the Web UI and a large percentage of the Global Schema Change Log would be log entries related to user settings. This information has been removed. Two, the typeahead functionality (which is widely but not exclusively used in the Web UI) generated very long running queries when the prefix matched nodes for which the user did not have privileges to view them. This has been fixed by capping the size of the request. And three, the health check Too Many Associated Objects was creating too many warnings about ChangeLog relations which were irrelevant to the user. This has been fixed.
This supersedes 2023.4-2024-12-04-13-44-49 and earlier versions.
If certain components are installed on a system and spot --upgrade was asked to plan an upgrade that included those components, then it would come up with an upgrade that was not actually possible. The problem was that the requirement for a different Java Runtime was not communicated via the dependency data that spot --upgrade uses to plan upgrades. This has now been rectified by making SPOT create the needed information for the software already on the system and by creating it for the available software, too.
This supersedes 2023.4-2024-11-27-16-19-07 and earlier versions.
Completed work to fix the healthcheck "Value links with dual visibility."
This supersedes 2023.4-2024-11-26-10-53-26 and earlier versions.
Now, a message about successful item transitions between states will be correctly shown in the Web UI when the user clicks on the Submit action with the Navigate To handler configured.
This supersedes 2023.4-2024-11-20-06-28-10 and earlier versions.
Fixed a problem in which an empty element incorrectly exported empty calculated values.
When running JavaScript business rules, there is a deadline for how long they are allowed to run. This mechanism had an error so that when stopping a business rule, in rare cases, it would not only cause the process running the business rule to fail but crash the entire server. This has been fixed.
This supersedes 2023.4-2024-11-19-13-42-08 and earlier versions.
When a setup object had externally maintained metadata attributes, the translation status would never be set to Up to Date. This has been fixed.
This supersedes 2023.4-2024-11-14-15-06-29 and earlier versions.
Fixed a problem occurring when Main events were not triggered for OIEP because its Event Queue still had an Approved triggering workspace configured. Now, changing a triggering workspace for OIEP will correctly synchronize a triggering workspace with OIEP event queue.
This supersedes 2023.4-2024-11-13-13-43-06 and earlier versions.
A problem in the 'Content missing value' healthcheck was found in fixed.
In cross-context exports, both local and inherited attribute values are exported as there may be some contexts without a local value. But this is only true if the attribute is dimension-dependent. If the attribute is dimension-independent, only the local value, if one exists, is now exported.
This supersedes 2023.4-2024-11-12-08-50-37 and earlier versions.
Backported an existing fix to NullPointerException when retrieving thumbnail asset to 2023.4mp1.
Fix for a problem in the 'Content missing value' healthcheck.
This supersedes 2023.4-2024-11-11-14-54-46 and earlier versions.
Fix for error preventing visibility of all configured Menu Groups in toolbar in Web UI when navigating to the corresponding screen for a first time.
This supersedes 2023.4-2024-11-07-10-23-44 and earlier versions.
An error occurred in which the Asynchronous Translation Processor was exporting reference nodes with approved changes along with specified nodes that also had approved changes. However, the event processor trigger configuration directed that the event processor should only start when a specific type of node and specific type of attribute on that node is changed. Therefore, the expectation was to export only the specified nodes. To correct the issue, on the translation configuration there is a code flag called immediateNodesOnly that controls which nodes should be retrieved for export. It was false, but now it is reverted to true. On false, the specified nodes and their references nodes are selected. On true, only the specified nodes are selected.
This supersedes 2023.4-2024-11-06-13-31-08 and earlier versions.
When a collection is included in a change package, the contents of the collection is no longer included.
This supersedes 2023.4-2024-11-01-14-54-41 and earlier versions.
In cross-context exports, the system exports both local and inherited references, as there may be some contexts without a local reference. However, this is only true if the reference is dimension dependent. If the reference is dimension independent, the system now only exports the local reference, if one exists.
Fixed a problem that occurred while configuring an export in which multivalued reference attribute values were incorrectly exported when using the Multi Valued reference mapping.
This supersedes 2023.4-2024-10-31-13-32-38 and earlier versions.
Hotfix HOTFIX-7901 doesn't have an approved description, yet. This is related to RDCDM-5908: Unexpected server error when click or hover over root nodes when configuring global data validations, ISSUE-740279.
This supersedes 2023.4-2024-10-30-14-33-20 and earlier versions.
When a historic-changes report is generated and it involves more than 50000 events then the processing is split into more batches. The final report now contains results from all batches.
This supersedes 2023.4-2024-10-25-12-07-00 and earlier versions.
Fixed a problem occurring when an ISO date attribute value could not be saved in Web UI on a Globally Configured Multi Edit Data Container component in the NL locale because of a failing verification check, which was caused by an incorrect and unnecessary conversion of ISO format to NL locale.
This supersedes 2023.4-2024-10-24-12-39-06 and earlier versions.
Hotfix HOTFIX-7882 doesn't have an approved description, yet. This is related to ISSUE-687959.
This supersedes 2023.4-2024-10-21-14-41-25 and earlier versions.
Adds a new deletion strategy; Partial deletion - which offers the user to select specific classifications for deletion. The classification ensures the deletion strategy is consistent for all products in the same version of ECLASS Advanced (ECA) - the configuration will ONLY work for the specific configured version of ECA. The logic is to recursively inspect all blocks and only delete those with classifications marked for deletion including all children. The logic must work on both aspects and blocks.
This supersedes 2023.4-2024-10-15-12-28-52 and earlier versions.
Fixed problem with session refresh in WebUI.
This supersedes 2023.4-2024-10-14-14-49-55 and earlier versions.
Hotfix HOTFIX-7791 doesn't have an approved description, yet. This is related to RD-24233: STEP failure resulting in wrong exit code.
This supersedes 2023.4-2024-10-09-13-36-27 and earlier versions.
Fixed a problem occurring when the Add Data Container action on a Web UI Data Container Multi Editor was throwing an exception if the user did not have privileges to view any of the Entity, Product, or Classification roots.
Fixed a problem occurring when the Hide Equal button on a Compare Records screen in Web UI was not hiding read only and non-read only date empty date values because of the date placeholder on a non-read only cell.
This supersedes 2023.4-2024-10-08-11-33-59 and earlier versions.
Hotfix HOTFIX-7850 doesn't have an approved description, yet. This is related to ISSUE-735353.
Hotfix HOTFIX-7858 doesn't have an approved description, yet. This is related to RD-24267: ISSUE-83044 - shadow issue - logout error .
This supersedes 2023.4-2024-10-03-19-50-30 and earlier versions.
Fixed a problem occurring when users with '/' characters in their ID were not able to perform an Advanced Search in Web UI due to search cache not being able to sanitize the corresponding file path.
This supersedes 2023.4-2024-09-30-13-37-43 and earlier versions.
Fix for rare cases where import might fail in an environment with multiple application servers doing import in an Oracle environment.
This supersedes 2023.4-2024-09-25-12-07-50 and earlier versions.
STEP Publisher (InDesign): Saving InDesign documents back to STEP could cause InDesign to hang if the document contained formatted text (e.g., bold or italic) using a paragraph style set to 'Adobe World-Ready Single-line Composer.' This affected both InDesign Client and InDesign Server.
This supersedes 2023.4-2024-09-24-08-14-55 and earlier versions.
Hotfix HOTFIX-7821 doesn't have an approved description, yet. This is related to ISSUE-719305, RD-24263: Please have a look at this certificate used for InDesign.
STEP Publisher (InDesign): Saving InDesign documents back to STEP could cause InDesign to hang if the document contained formatted text (e.g., bold or italic) using a paragraph style set to 'Adobe World-Ready Single-line Composer.' This affected both InDesign Client and InDesign Server.
Now, a Web UI Title Header with a custom label will preserve this label when being exported via Export Current View action in Web UI.
This supersedes 2023.4-2024-09-23-06-02-40 and earlier versions.
STEP Publisher (InDesign): Saving InDesign documents back to STEP could cause InDesign to hang if the document contained formatted text (e.g., bold or italic) using a paragraph style set to 'Adobe World-Ready Single-line Composer.' This affected both InDesign Client and InDesign Server.
This supersedes 2023.4-2024-09-20-09-51-21 and earlier versions.
Fixed a problem occurring when the UNSPSC converter was throwing an exception when parsing invalid lines in the input file. Now, such lines (which do not correspond to the number of columns) will be ignored.
This supersedes 2023.4-2024-09-18-11-44-28 and earlier versions.
Fixed problem occurring when OIEP event processing was stopped if processed event did not have an output template, and the OIEP was configured with batch size = 1. In this case, the EP was ignoring such event but did not pick the next events.
This supersedes 2023.4-2024-09-05-12-56-43 and earlier versions.
Fixed a problem occurring when the frequent deletion of a Web UI alert notification caused a lot of changes to Change Logs, which could cause memory and performance problems. Now, Web UI Alert Notifications deletions will not trigger the change log deletion event.
Hotfix HOTFIX-7771 doesn't have an approved description, yet. This is related to RD-24253: ISSUE-82060 shadow issue.
Fixed unexpected EmptyStackException, which appeared when replaying the import after catching the optimistic-lock exception sporadically.
The code that checks which references should be removed from MongoDB fails to transform a Mongo Document object to a compatible Java object when a single value reference is deleted from an Entity. The code change now can handle the deletion of both single-value and multi-value references.
Corrected the behavior for mixed values/ overlapping values.
The code that checks which references should be removed from MongoDB fails to transform a Mongo Document object to a compatible Java object when a single value reference is deleted from an Entity. The code change now can handle the deletion of both single-value and multi-value references.
Hotfix HOTFIX-7794 doesn't have an approved description, yet. This is related to RD-24255: Hotfix for ISSUE-77486.
Added missing 'Added to PDX' Value in PDX Data Container after retrieving historical data from PDX to STEP.
Fixed a bug for Oracle-based STEP systems, where - in some situations - could make STEP fail to revert an object with references to a previous version.
Now, 'Approve Action' on a Web UI Node Editor will be enabled correctly after adding / removing / making a local attribute link.