These are the 81 updates to saas in version 2024.4, sorted with newest version first:
This supersedes 2024.4-2025-05-01-19-03-20 and earlier versions.
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.
This supersedes 2024.4-2025-04-30-15-51-40 and earlier versions.
Elasticsearch libraries are not supported on the single-tenant servers. The libraries were downgraded.
This supersedes 2024.4-2025-04-30-09-09-25 and earlier versions.
Fixed an unexpected exception shown for the Web UI Add Data Container popup when editing non-LOV multivalued attributes.
This supersedes 2024.4-2025-04-29-08-39-37 and earlier versions.
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.
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 with split transformations in the exporter mapping. The problem was that the result value was empty when there was no delimiter in the value.
This supersedes 2024.4-2025-04-28-13-59-15 and earlier versions.
Currently, if none of the context-dependent attributes in ES config are marked as 'Display Data,' FullText search will not work on them because mappings will not be directly generated. This fix resolves this issue and now, context-dependent FullText search will no longer be dependent on publishable / displayed data.
Adding sanitization to XML tags to allow special characters in IDs. Now, Elasticsearch will be able to export data even if they include characters like &, <, or >.
This supersedes 2024.4-2025-04-25-10-57-47 and earlier versions.
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.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
Fixed an issue in which InDesign plugins crashed due to a NullPointerException error.
General improvement to remove unused system code.
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.
This supersedes 2024.4-2025-04-24-19-48-09 and earlier versions.
Now, filtering works correctly for the Table Header Business Function on Web UI Node Lists.
If an SFTP delivery fails, then the server will retry to do the delivery, dependent on the error condition.
Fixed a NullPointerException, which was thrown during the export of an empty LOV.
This supersedes 2024.4-2025-04-23-11-27-56 and earlier versions.
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.
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.
Fixed s setback, which caused an unexpected exception on a Web UI Node Editor with a Data Container popup component for read-only users.
This supersedes 2024.4-2025-04-22-19-14-09 and earlier versions.
Security update for library used in the admin portal.
Security update for a library used in the core component
Updates a library used in server configuration
This supersedes 2024.4-2025-04-16-13-03-16 and earlier versions.
Fixed a reloading error that occurred in the Compare view when filtering was applied.
Fixed the BMEcat export result file, which should not contain ARTICLE_TO_CATALOGGROUP_MAP tag without corresponding ARTICLE tag.
This supersedes 2024.4-2025-04-15-09-29-54 and earlier versions.
The fix is to allow the export of external DAM asset content (previously, the exports were failing with an unexpected exception).
Fixed unexpected exception when downloading external asset with a URL longer than 100 characters via Asset Download Home bind in business rules.
This supersedes 2024.4-2025-04-11-19-47-25 and earlier versions.
Fixed a NullPointerException that occurred when editing import configurations in the workbench with multiple data containers and variable mapping.
When a business action with a value generator was run from an IIEP, the value generator would not see the imported data. This has been 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.
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.
This supersedes 2024.4-2025-04-09-14-04-53 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.
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 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 validation for LOVs with IDs on a Web UI Node Editor Attribute Value component for LOV attribute with more than 5,000 values.
Performance fix related to the poller process that resumes asynchronous jobs. The issue was that when there were a large number of translation jobs, it took a long time to find the jobs to resume. This fix uses cache to reduce the time complexity to be linier instead of squared, and it uses nested transactions so jobs that have already been identified as 'should be resumed' can be started immediately - instead of having to wait for all the jobs to be analyzed.
This supersedes 2024.4-2025-04-09-09-34-02 and earlier versions.
Fixed a NullPointerException occurring in PIES imports following an update.
This supersedes 2024.4-2025-04-08-15-18-22 and earlier versions.
General security improvements have been implemented to enhance the overall security of our systems.
In rare cases, there has been a problem where a certain internal report would run for a long time and block memory cleanup - potentially causing out-of-memory exceptions. This has been changed, so that the report no longer blocks memory cleanup during the entire report generation. Additional logging has also been added to help identify other issues that might block memory cleanup.
Fixed JavaScript Vulnerabilities on bridge
Performance fix related to the poller process that resumes asynchronous jobs. The issue was that when there were a large number of translation jobs, it took a long time to find the jobs to resume. This fix uses cache to reduce the time complexity to be linier instead of squared, and it uses nested transactions so jobs that have already been identified as 'should be resumed' can be started immediately - instead of having to wait for all the jobs to be analyzed.
This supersedes 2024.4-2025-04-07-14-12-48 and earlier versions.
To correct an issue related to a DUNS number error, DNB text attribute values are now only truncated if the value contains more characters than the defined “Maximum Length."
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.
General security improvements have been implemented to enhance the overall security of our systems.
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).
Now, the old Elasticsearch reindexing processes will be correctly deleted automatically, allowing reindexing to start again.
Fixed a problem in which datasheet PDF creation caused an error when using the "Approved" workspace.
This supersedes 2024.4-2025-04-07-00-24-48 and earlier versions.
Fixed a problem that occurred when the "hostname" parameter was not restored correctly from the delivery configuration during SFTP Translation delivery.
This supersedes 2024.4-2025-04-03-14-33-58 and earlier versions.
Add support for 'Enhanced Content' tag
In rare cases, there has been a problem where a certain internal report would run for a long time and block memory cleanup - potentially causing out-of-memory exceptions. This has been changed, so that the report no longer blocks memory cleanup during the entire report generation. Additional logging has also been added to help identify other issues that might block memory cleanup.
Security update to fix potential vulnerability
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 2024.4-2025-04-02-10-08-31 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.
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.
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.
After implementing a fix to correct an issue in which the STEP API returned a code 500 with an invalid access token, Keycloak will now return a 401 status code in case of an invalid bearer token.
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.
Fixed JavaScript Vulnerabilities on bridge
Now, it is possible to change the default limit of tokens in GraphQLv2.
This supersedes 2024.4-2025-04-01-16-45-01 and earlier versions.
Fixed an unexpected IOException ("invalid distance too far back") which occurred during an Outbound Business Rule Message Processor concurrent execution.
Implemented a security update for the system.
Overridden calculated attributes were not included in exports if "Include Calculated Attribute Values" was not selected. This has been fixed.
Fixed retrieving PDF XMP metadata properties acc. to format of file: application/pdf after uploading Asset in workbench.
This supersedes 2024.4-2025-03-31-13-57-34 and earlier versions.
General improvements have been implemented to enhance the overall security of our systems.
Removed unnecessary checks to single-tenant Elasticsearch.
This supersedes 2024.4-2025-03-28-11-43-00 and earlier versions.
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.
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.
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
This supersedes 2024.4-2025-03-27-12-46-34 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 setback related to exiting edit mode on Multi Edit Display mode in the Web UI.
This supersedes 2024.4-2025-03-26-19-57-55 and earlier versions.
Fixed issue with vertical scaling in SaaS v2 environments.
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.
This supersedes 2024.4-2025-03-26-10-50-32 and earlier versions.
To correct the null pointer exception issue, the Kafka Receiver plugin can now optionally skip null values from Kafka.
security update to tpl
Fixed a problem where the price list was ignored when performing an eCatalog export.
This supersedes 2024.4-2025-03-25-19-13-22 and earlier versions.
Only relevant for STEP running on Cassandra. Improved Cassandra GC to retry if getting errors (timeout,tombstone,etc) during token range scan. This will ensure DB is cleaned properly after deleting objects in STEP.
General security improvements have been implemented to enhance the overall security of our systems.
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.
This supersedes 2024.4-2025-03-24-13-26-57 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.
Added additional logging to the Search screen Excel export BGP.
Fixed a NullPointerException occurring in PIES imports following an update.
This supersedes 2024.4-2025-03-21-15-28-37 and earlier versions.
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.
General security improvements have been implemented to enhance the overall security of our systems.
This supersedes 2024.4-2025-03-20-17-14-30 and earlier versions.
Now, AND Object Type searches on Advanced Search screen will return valid results and will not behave as OR searches.
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 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.
This supersedes 2024.4-2025-03-20-10-03-06 and earlier versions.
Now additional privileges are not required to export manual Excel translationsfor LOVs with IDs.
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.
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.
This supersedes 2024.4-2025-03-19-06-20-16 and earlier versions.
Fixed an incorrect time conversion occurring in state logs when servers were not running in UTC.
Using Edit Asset to edit an image worked correctly the first time, but would continue to bring up the first image when editing other images. To fix the issue, the UI object is updated when fetching the thumbnail so the interface shows the proper object.
This supersedes 2024.4-2025-03-15-10-36-17 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 issue that caused the faulty parsing of PDF files.
Now, invalid characters from an endpoint name will be escaped when creating temporary files for export.
Using Edit Asset to edit an image worked correctly the first time, but would continue to bring up the first image when editing other images. To fix the issue, the UI object is updated when fetching the thumbnail so the interface shows the proper object.
Fixed an EmptyStackException during the import replay and added logging for further investigation if the issue ever recurs.
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.
Now, a Multi Value Editor on the Multi Context screen will correctly save chosen values.
Added DAM variant of pipelines for web-proof-small and web-proof-medium.
This supersedes 2024.4-2025-03-14-10-51-13 and earlier versions.
Fixed a problem with hot deployment of customer-developed components causing background process executor to be shut down.
This supersedes 2024.4-2025-03-13-14-57-39 and earlier versions.
Fixed a NullPointerException occurring in the Generic XML import.
This supersedes 2024.4-2025-03-12-07-03-10 and earlier versions.
Increasing lifespan of the Elasticsearch reindex background processes to avoid situations where customers cannot check their history or retry a failed BGP after passage of time.
This supersedes 2024.4-2025-03-06-14-07-24 and earlier versions.
This supersedes 2024.4-2025-03-05-14-52-08 and earlier versions.
Now, the material menu will be correctly expanded to the left when there is more than one submenu.
Now read-only ISO Date and time attribute values will be shown correctly (aligned with non-read-only) on the Web UI Node Editor.
Fixed unexpected problems occurring when applying conditional validity caused multi-value attributes on a Web UI Node Editor marked as changed.
Fixed a problem where it appeared that you could not create a context in STEP Workbench, but in fact, the context already existed. The error was just not reported.
Using Edit Asset to edit an image worked correctly the first time, but would continue to bring up the first image when editing other images. To fix the issue, the UI object is updated when fetching the thumbnail so the interface shows the proper object.
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.
It is now possible to run autopagination with a publication template with 5 columns and mount of a number of items with tables.
For LOVs with more than 5,000 values, the classification filter would be ignored and invalid values were displayed and could be selected. Now, inherited filters from classifications will be respected when deciding whether to show an LOV as a typehead or a dropdown on the Web UI Node Editor.
This supersedes 2024.4-2025-03-04-19-18-16 and earlier versions.
When importing data using mapping, when using two intermediate variables, the second mapping overwrote the first mapping. We have now fixed it so that we prevent this.
Fixed the issue in BMEcat export where the
Fixed issue where revision purging by date would leave behind a revision that should have been purged.
This fix stops NullPointerExceptions from the Kafka Streaming Receiver Controller when the controlling background process has been deleted.
Fixed reading messages from a Kafka topic with zstd compression enabled.
This supersedes 2024.4-2025-03-03-21-56-25 and earlier versions.
If some configurations were mistakenly marked 'preset' while being owned by a user, reading of the configurations would fail. This means that the configurations would not show up in the Instrument Configuration tool. This is now fixed.
Removing a reference suppression in the Web UI would fail if it was performed from a Multi Reference component configured to display "Referenced By" references. This has been fixed.
This supersedes 2024.4-2025-02-28-13-43-41 and earlier versions.
Fixed issue where revision purging by date would leave behind a revision that should have been purged.
In rare cases, there has been a problem where a certain internal report would run for a long time and block memory cleanup - potentially causing out-of-memory exceptions. This has been changed, so that the report no longer blocks memory cleanup during the entire report generation. Additional logging has also been added to help identify other issues that might block memory cleanup.
This supersedes 2024.4-2025-02-26-16-44-32 and earlier versions.
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.
This supersedes 2024.4-2025-02-25-08-52-45 and earlier versions.
Added logging to facilitate troubleshooting for GDSN publisher.
Added log information to integration endpoints to enable troubleshooting of errors
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.
This supersedes 2024.4-2025-02-24-14-39-40 and earlier versions.
A Cassandra-specific problem for the code to postpone events has been fixed.
This supersedes 2024.4-2025-02-21-13-23-10 and earlier versions.
Fixed a bug occurring when adding a new Data Container instance from the Globally Configured Multi Edit Data Container component in Web UI, which contains a multivalued LOV attribute and this attribute has more than one value.
When a Web UI Globally Configured Multi Edit Data Container uses Reference Header with Reference Type, which contains dot or dots, the user could see an error pop-up after loading the component or changing one of Data Container instance values or references. This has been corrected. Now, there will not be any error pop-up when a Globally Configured Multi Edit Data Container is configured and contains a Reference Header with Reference Type which contains dot(s).
A Cassandra-specific problem for the code to postpone events has been fixed.
This supersedes 2024.4-2025-02-19-12-44-22 and earlier versions.
BMEcat exporter now avoids incomplete asset references for non-existing asset sources.
When a workflow-wide audit message business action was configured for a workflow, audit messages would not get sent for the automatic transitions from a parallel workflow to the contained workflow clusters and to the initial states of those clusters. Now, audit messages are also sent for these transactions.
Fixed the problem where attribute names are exported with incorrect language when using BMEcat export.
BMEcat exporter now avoids incomplete asset references for non-existing asset sources.
This supersedes 2024.4-2025-02-18-12-59-04 and earlier versions.
It was not possible to get the ID of a value of a List of Values in AttributeLink, because the extValues document for the AttributeLink was not exported. Now, the JSON Converter is changed so that the extValues document for the AttributeLink will be exported. Then, the LOV value ID will be accessible.
After the fix, it is possible to approve changes of the parent of the node in the 'Partial approve' component.
Fixed a problem where an ID prefix was incorrectly added to a PDF object name when creating a data sheet.
Importing a product that was in the recycle bin under a different parent would fail with a JDOOptimisticVerificationException. This has been fixed.
This supersedes 2024.4-2025-02-17-16-31-55 and earlier versions.
Fixed a problem, when alerts, shown by using the Run Business Action on Web UI Node Editor, were cleaned up when evaluating validation business conditions on the same screen.
Fixed issue where import files would sometimes be ignored by the GDSN importer.
Fixed a problem when Multi Value sub-presenters did not reflect their validity correctly, which means that cleaning validation errors did not enable corresponding buttons (Save, Approve, etc.) on a Web UI Node Editor screen.
When using a Web UI Globally Attribute Value Component for a multivalued LOV with IDs attribute and there is Validation Business Condition with Data Validation Binds configured, changing the component state from Read Only to Mandatory caused existing values to be not visible. This issue has been fixed, and rows for existing values are now correctly presented in the Web UI.
After the fix, it is possible to approve changes of the parent of the node in the 'Partial approve' component.
When using a Web UI Globally Configured Multi Edit Data Container with a configured Validation Business Condition, a user could see an error pop-up for a short time after adding new instance of a Data Container. This has been corrected. Now, there is no error pop-up after adding a new Data Container instance.
This supersedes 2024.4-2025-02-11-13-37-47 and earlier versions.
Fixed an issue related to expiration times on OAuth (Open Authorization) tokens passed to the Kafka client. Faulty expiration times were causing a token-refresh error on long-running connections.
Added more logging to investigate Business Rule loop.
Fixed a problem with InDesign server plugins where tables were removed during duplication when they contained a nested STEPCOND statement.
After the fix, it is possible to approve changes of the parent of the node in the 'Partial approve' component.
Specific incompatibilities within JavaScript Business Rules in relation to the Java21 upgrade were addressed.
It has been seen that extensions / customizations of the REST API has been generating very large responses. This is a problem, as the responses are held in heap memory. This fix will ensure that a REST API call will not consume much more than 100Mb. If it does, it will be terminated with an error - in order to protect the application server from running out of memory.
Fixed the problem where attribute names are exported with incorrect language when using BMEcat export.
Fixed an issue related to expiration times on OAuth (Open Authorization) tokens passed to the Kafka client. Faulty expiration times were causing a token-refresh error on long-running connections.
Now, an empty node collection profile will be updated correctly.
Introduced a possibility to disable a replay during the import in case of a business condition rejection - to avoid a situation when a business condition sends an email twice. In order to enable this possibility, submit a Stibo Systems Service Portal ticket.
In rare cases, the health check in the admin portal may report false positives for ‘Unused Pseudo Workspaces,’ resulting in inconsistent data being falsely reported. This has now been corrected.
This supersedes 2024.4-2025-02-10-15-46-38 and earlier versions.
Addressed XSS vulnerability when creating / duplicating users on User List screen in Web UI.
Fixed a setback that made the Globally Configured Multi Edit Data Container component in Web UI ignore width dimensions of table headers configured for this component.
Addressed XSS vulnerability in Web UI Alert Notifications.
Now, the amount of classification children returned by Browse tab in a Smartsheet will be limited to avoid memory consumption.
Fixed an infinite loop when processing conditional validity events on a Web UI Node Details screen.
Addressed XSS vulnerability when creating an Attribute / Attribute group in Web UI.
Now, the leading zeros will be shown for the DUNS Number header on the Web UI D&B Match Candidates Screen, if the leading zeros were enabled on a system.
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 2024.4-2025-02-05-17-51-53 and earlier versions.
Fixed a problem that occurred when values longer than 4000 bytes were entered in Cassandra-based STEP systems. Prior to this fix, a small window of opportunity existed that could cause the system to produce an error like, "Unable to find blob segment..." because the blob content could be written shortly after the value object. This is now fixed.
When using 'Cloud Blob Storage Delivery' with a 'Blob Storage file path template' containing $timestamp, it is now the same timestamp used in the BGP log file messages about the file delivery and the file path used in the blob storage container.
Fixed exception-handling issue that occurred when failing to close the connection after an unsuccessful JMS message download.
Hotfix HOTFIX-8099 doesn't have an approved description, yet. This is related to ISSUE-734972.
When doing a Lionbridge translation, the background processes in Quarantine state will no longer block for retranslation of an object.
When doing a Lionbridge translation, the background processes in Quarantine state will no longer block for retranslation of an object.
Internal fix for CI/CD synchronization.
The requirement for the stibosw user to run commands as root has been removed and so has the configuration of sudoers that allowed it.
Web UI users will no longer get an unexpected error when expanding the PDS channel status row. This is fixed by refactoring toggle display logic by replacing jQuery based DOM manipulation with native JavaScript methods.
A fix was made that will make the error message a better when you have a cycle in the hierarchy, so that you can see the path with the cycle.
Before fix: When resolving the path for the FrontPublicationSectionImpl with id
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.
The situation where InDesign shows the “moveItemsToNewLocation adjust loop didn't terminate error” when a table with a header repeating pagination plugin is justified has been solved.
Added more logging to investigate a future potential JWT token desynchronization problem.
This supersedes 2024.4-2025-01-29-14-51-22 and earlier versions.
Added missing dependency to Apache POI. Its absence made the Excel Import component fail in Web UI when uploading an Excel file.
Added a null check to account for issues with this fix: Fixed state of buttons with Enforce Validity enabled when an attribute is mandatory by a data validation business condition and its value was removed.
The Context Splitter Post Processor was outputting empty MultiValue XML nodes for inherited values that should NOT be exported at all, because there are local values defined on the attribute. The solution is a change to how the Context Splitter Post Processor calculates when to do an export of a MultiValue XML node, so that if there are local values on an attribute, there should be no MultiValue XML nodes with the XML attribute Inherited='#'.
Decreased memory usage when running multiple parallel Match and Merge threads which calculate Decision Table business functions.
Encountered an issue that caused data to be imported incorrectly into data containers. To fix the issue, mapping multiple data containers of the same type from multiple columns via mapped variables was implemented.
Now, the amount of classification children returned by Browse tab in a Smartsheet will be limited to avoid memory consumption.
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.
Added more logging to investigate Business Rule loop.
A file created by the XSLT postprocessor could not be deleted from an Azure filesystem. This has been fixed.
Added log information to integration endpoints to enable troubleshooting of errors
Fixed issue where values generated in an algorithm value generator would not check if it had generated before.
When using a Web UI Globally Configured Multi Edit Data Container with a configured Validation Business Condition, which sets a data container object's attribute as mandatory. Deleting the value of such an attribute would enable the Save Action button and/or Approve Action button even though Enforce Validity is enabled. This has been corrected. Now, both buttons are disabled when Globally Configured Multi Edit Data Container mandatory attribute values are removed. This prevents the system from storing empty values in a database for data container object's attributes with conditional mandatory state.
Fixed an unexpected exception that was thrown when performing a wildcard search of a search string, which contained single backslash characters. This exception was thrown by the In-Memory search.
A better user-friendly message was added and an import should continue when trying to change ownership of classification to product links in Cassandra.
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.
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.
Fixed an infinite loading problem when resizing a browser window with a Node List, which has table headers with configured dimensions.
Fixed the issue in BMEcat export where the
Fixed a NullPointerException occurring when opening the Globally Configured Multi Edit Data Container without data container objects in Web UI.
Introduced a solution to show local business rules in a System Setup Recycle Bin in workbench. To enable this functionality, contact Stibo Systems Support.
This supersedes 2024.4-2025-01-28-19-31-20 and earlier versions.
Fixed an issue related to expiration times on OAuth (Open Authorization) tokens passed to the Kafka client. Faulty expiration times were causing a token-refresh error on long-running connections.
Fixed an issue related to expiration times on OAuth (Open Authorization) tokens passed to the Kafka client. Faulty expiration times were causing a token-refresh error on long-running connections.
Properties from ExtraDriverOptions will overwrite settings from the plugin configured in the workbench.
This supersedes 2024.4-2025-01-27-10-31-18 and earlier versions.
Fixed a problem occurring when Elasticsearch indexing could fail if STEP Context IDs contained a backslash character, causing problems with file creation.
Fixed a problem occurring when the Read Only Attribute value, representing an ISO Date / Time attribute on a Web UI Node Editor / Unfolding Data Container component was showing a local browser time instead of the same time as in workbench.
Fixed a problem occurring when a Business condition, which applies Mandatory status on a Web UI Node Editor, was hiding the warning messages about invalid values for LOV attribute.
Fixed a problem where the Menu Group component's actions were not always saved in Web UI design mode on a Node List screen.
This supersedes 2024.4-2025-01-24-14-11-59 and earlier versions.
There was an issue in which STEP Extension API Async Example did not work due to incompatibility with Java. The compatibility issue has been fixed.
There was an issue in which STEP Extension API Async Example did not work due to incompatibility with Java. The compatibility issue has been fixed.
This supersedes 2024.4-2025-01-23-13-37-05 and earlier versions.
Fix to allow exceptions thrown by JavaScript code, as opposed to a public API call, from within a library to fall though an executeInContext call and be ignored.
Made it impossible to delete the Publication hierarchy root. This should not be deleted, as STEP relies on it being there - and you get strange errors if it is missing.
BMEcat exporter now avoids incomplete asset references for non-existing asset sources.
Fix to allow exceptions thrown by JavaScript code, (as opposed to a public API call), from within a library to fall though an executeInContext call and be ignored.
BMEcat exporter now avoids incomplete asset references for non-existing asset sources.
Now, potential problems with endpoints cache will not fail the IIEP BGP and will not cause it to have a 'completedwitherrors' status. Added more logging to investigate cache problems.
This supersedes 2024.4-2025-01-22-14-32-19 and earlier versions.
This supersedes 2024.4-2025-01-21-19-44-25 and earlier versions.
Fixed issue where values generated in an algorithm value generator would not check if it had generated before.
This supersedes 2024.4-2025-01-20-13-48-29 and earlier versions.
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.
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.
Made workbench bootstrap improvement.
Added support for import of attributes / properties of URI_TYPE_Type, which broke the import. The general policy is changed to report unknown base validation types as errors but continue imports regardless.
Improved Workbench bootstrap performance.
Fixed a problem occurring when workflow business rules were marked as invalid if a workflow had a mapping without any states.
Fixed XSS vulnerability of searchURL parameter, which can be used to execute dangerous code on a Web UI Advanced Search screen.
Fixed a problem occurring when workflow business rules were marked as invalid if a workflow had a mapping without any states.
Increased performance by limiting the amount of assets loaded when expanding a classification in the workbench.
Fixed French translation of STEP Workbench.
This supersedes 2024.4-2025-01-20-09-07-45 and earlier versions.
This fix is for an issue encountered when removing the reference promotion to a Golden Record. The Golden Record did not reflect changes on references removed from the child node.
Customer may use M&M Web Service to import Merged Golden Records. If FINE or FINEST logging is enabled for matching component, service could fail with exception. It is fixed now.
When exporting tables using OIEP, with Table Type Definitions export size set to minimum, Table Types will now be exported for all exported tables, except suppressed tables.
This fix is for an issue encountered when removing the reference promotion to a Golden Record. The Golden Record did not reflect changes on references removed from the child node.
A fix was put into place to ensure a major revision is created on initial non-major revisions while merging records. This means that data will not be lost from the revision history.
An adjustment was made in the process of getting ML Match Recommendations: Training failure results in the whole recommendation process failure and does not trigger fail / retry logic.
By default, all cross-context exports always contain suppressed references. Following configuration property has been added in order to omit those references: ExportManager.Omit.SuppressedReferences.CrossContext=true
The new health check plugin 'Invalid name' has been added. It can find and fix nodes with names that do not have the correct dimension dependencies according to the definition of the object type.
By default, all cross-context exports contain suppressed references. In order to omit those references, the following configuration property has been added: ExportManager.Omit.SuppressedReferences.CrossContext=true
When exporting tables using OIEP, with Table Type Definitions export size set to minimum, Table Types will now be exported for all exported tables, except suppressed tables.
Now, survivorship business rules that are trying to queue events will be ignored during unmerge, as it is not possible for non-persistence objects.
Fixed a problem where an edited cell of a Web UI Node List did not have a proper scrollbar.
The user was not able to see all data issue error messages from the server in the SaaS setup. This has now been fixed.
Matching and Merging Web Service call ceased to work if FINE logging for the matching component was enabled on the system. This has been fixed.
Reintroduced support for gamma attribute on import of PNG images.
Fixed a bug that in certain circumstances could produce a NullPointerException. This could happen for long-running operations where hard-evicts had been performed.
Fixed a bug that would cause an error when loading the Web UI with a Reference Metadata Flex Value Header configured in the Multi Reference component.
Now, it is possible to enable filtering for Assignee Table Header on a Web UI Node List in cases where the Node list is very big. To enable this, contact Stibo Systems Support.
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 2024.4-2025-01-18-17-55-39 and earlier versions.
Corrected the third-party libraries (upgrade) to support API changes and avoid NoClassDefFound exceptions while working with zip files.
This supersedes 2024.4-2025-01-16-18-29-51 and earlier versions.
Added option for hot-swapping recipe through the system-management API for single-node SaaS systems.
When working with very large collections, the In-Memory database could run out of memory, causing the application to crash. This has been fixed.
There has been an issue on tripod and bipod systems where the metric inmemory.memoryused.bytes would only show the used bytes for one of the pods. This has been fixed, so now it shows the sum of bytes used by all pods in the system.
This supersedes 2024.4-2025-01-14-13-06-15 and earlier versions.
Fixed unexpected NullPointerException thrown by GWT when sporadically navigating amongst the Tree Navigator in Web UI.
In Instrument when users navigate to the 'Work Areas & Perspectives' tab in configuration tool, certain configured perspectives were not appearing. This issue was caused by an ownership issue in the work area configuration. The problem has now been resolved, ensuring that all configured perspectives are displayed as expected.
Additional diagnostic data has been added to help diagnose the root cause of the problem where Proof View is throwing an internal error.
This supersedes 2024.4-2025-01-13-19-51-46 and earlier versions.
Fixed an issue in which value generators would get into an optimistic lock when creating and applying a value generator to an object in a business action.
This supersedes 2024.4-2025-01-09-19-08-46 and earlier versions.
Asset Premigration: Fixed error when handling an asset having a huge content size (more than INT_MAX bytes).
This supersedes 2024.4-2025-01-07-20-52-08 and earlier versions.
Now, context / workspace from a Web UI URL will be properly decoded, which will fix a reason for wrong error messages about incorrect context / workspace ID.
Improved performance for the Compare Records screen with Show Only Valid and Render Only Valid set.
Enabled choosing next packaging item in the packaging hierarchy editor in Web UI.
Fixed a NullPointerError occurring when retrieving a config property without documentation - and log it instead.
Now, server-side delivery will work correctly with Smartsheet export format.
The EQ and EVP audit trail logs have been combined.
This supersedes 2024.4-2025-01-06-11-16-20 and earlier versions.
For multi-queue environments, we added the ability to serialize specific background process queues.
Fixed a problem in which the export contained duplicate values when exported with a saved export configuration for CSV files.
With multiple batches in an event based endpoint, the customer got the same name on the millisecond, causing duplicate file name issues in the downstream system. The endpoint failed and stopped running. To fix this, a new substitution variable ($uuid) that can be used to ensure unique file names are generated in delivery plugins was added. As an example, the format of these uuid are like "d36c9b1a-4c69-47e2-baa8-336af2e299e8".
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.
Added additional server logging for bulk update to log the stack trace of the exception when an OptimisticLockException occurs during the bulk-update service.
Fixed a problem where it was not possible to save an LOV value with an ID via a Reference Metadata header.
By default, all cross-context exports always contain suppressed references. Following configuration property has been added in order to omit those references: ExportManager.Omit.SuppressedReferences.CrossContext=true
Now, an exception will not be thrown if a business rule is trying to trigger an event for a Non-Persistent Object as a part of a Survivorship rule, executed on an Advanced Merge Screen.
There was a problem with the "create references" call. It did not properly rollback the changes in case of an error. This is now fixed.
Fixed a problem that occurred when the state transition date was shown incorrectly in the STEP Workbench.
Hotfix HOTFIX-7998 doesn't have an approved description, yet. This is related to RDSUP-360: SETBACK: Incorrect warning message in workflow designer.
For multi-queue environments, we added the ability to serialize specific background process queues.
Fixed a problem with missing clipping path images in a converted image when the output was set to create .tiff files.
Fixed retrieving PDF XMP metadata properties acc. to format of file: application/pdf after uploading Asset in workbench.
Fixed a problem in which the export contained duplicate values when exported with a saved export configuration for CSV files.
By default, all cross-context exports contain suppressed references. In order to omit those references, the following configuration property has been added: ExportManager.Omit.SuppressedReferences.CrossContext=true
By default, all cross-context exports contain suppressed references. In order to omit those references, the following configuration property has been added: ExportManager.Omit.SuppressedReferences.CrossContext=true
Fixed a problem in which the export contained duplicate values when exported with a saved export configuration for CSV files.
Fixed a bug using translated messages as input for Data Issues Report header in business rules.
Fixed an issue where vertical scrollbars were not displaying on lookup tables by adding a scroll pane and aligning elements in the transformation configuration editor.
Fixed the healthcheck plugin "Softvalues with Dual Visibility" so that it does not fail with the exception "SnapshotTooOldException" when the number of rows in the softvalue table is large.
Added additional logging to find out which exception to whitelist.
Fixed problem that occurred when the state transition date was shown incorrectly in the STEP Workbench.
Fixed problem that occurred when the state transition date was shown incorrectly in the STEP Workbench.
Fixed a problem where the wrong products were being added to BMECAT 1.2 export.
Fixed French translation of STEP Workbench.
Fixed a problem occurring when hotfolder cache was not respecting the IN folders. If different IIEPs used the same hotfolder with different IN subfolders, a cache file was used by all of them, which lead to unexpected errors.
Fixed a problem occurring when workflow business rules were marked as invalid if a workflow had a mapping without any states.
Fixed a problem occurring when a Privilege Error was shown in workbench when a user clicked to Partial Approve on a node, which only had unapproved Table Text part objects, which were not available for partial approve.
Fixed a problem with missing clipping path images in a converted image when the output was set to TIFF.
A "changes" attribute has been added to the AssetType validation schema for STEPXML so that exported STEPXML containing this character will not fail validation when imported again.
Fixed an issue where vertical scrollbars were not displaying on lookup tables by adding a scroll pane and aligning elements in the transformation configuration editor.
Fixed a problem occurring when workflow business rules were marked as invalid if a workflow had a mapping without any states.
Fixed a problem in which the export contained duplicate values when exported with a saved export configuration for CSV files.
This issue occurred when exporting BMEcat in workbench. The issue was that STEP exported Feature elements with only Fname elements even when there was no non-empty values for the Feature. This is now fixed.
This supersedes 2024.4-2025-01-03-21-45-11 and earlier versions.
Improved performance when initializing a Globally Configured Multi Edit Data Container on a Web UI Node Editor screen.
Fixed a setback, which allowed users to export table headers without values via the Export Current view action when the 'Allow Empty values' design mode parameter was disabled.
Fixed a problem where an attribute value header was hidden if it was not valid for the first item displayed on an Advanced Search screen in Web UI.
Added translation to 'Last edited by' text in a Product Summary Card by including a current user in all the supported languages.
HOTFIX-7955 was backported to to:automotive/7.0/automotive-7.0.52.spr (11.1-related automotive version).
Now, the Table Header References component will be shown as read only for users who do not have privileges to add / delete references.
Introduced a possibility to change the default encoding of CSV files imported via the Import Widget on a Web UI Homepage. To change this encoding, contact Stibo Systems Support.
Fixed a sporadic problem occurring when the date picker for ISO Date / Time attributes in a Web UI References component was not closed sometimes after picking the value.
Fixed a bug using translated messages as input for Data Issues Report header in business rules.
Fixed a problem occurring when the Referenced Asset representation component was not shown on a Web UI Initiate Item screen.
This supersedes 2024.4-2024-12-30-13-26-40 and earlier versions.
When doing a search that returns more results than can be displayed, the total number of results reported could be higher than the actual number of results. This has been fixed.
Fixed a bug in the lock mechanism used by InMemory STEP systems. On clustered STEP systems with more than one server, the lock mechanism could, in very rare cases, cause a deadlock resulting in background processes and other operations getting stuck. The only solution to this was to restart one or more of the servers. This issue has been fixed.
STEP sometimes failed during shutdown. It was possible for running processes in rare cases to prevent the shutdown from shutting down nicely and it that case the shutdown would first complete after the hard deadline of 30 minutes thus delaying restart procedures. This has been fixed.
This supersedes 2024.4-2024-12-20-09-32-34 and earlier versions.
Hotfix HOTFIX-7991 doesn't have an approved description, yet. This is related to RDSUP-386: Elasticsearch: BAs are disabled on Search Screen.
An improved error message was added for when the splitter business action for a business action Event Processor did not call the addMessage() method. Instead of a NullPointerException, a meaningful error message will be shown in the execution log.
Fixed a problem occurring when a warning message about reaching a value generator threshold was not sent to the configured email address.
If you have a loop in your publication sections, you could get an internal error. This fix makes sure a message is logged in the application server log instead of throwing an error.
An improved error message was added for when the splitter business action for a business action Event Processor does not call the addMessage() method. Instead of a NullPointerException, a meaningful error message will be shown in the execution log.
This supersedes 2024.4-2024-12-17-13-27-51 and earlier versions.
This supersedes 2024.4-2024-12-12-19-52-29 and earlier versions.
Hotfix HOTFIX-7993 doesn't have an approved description, yet. This is related to RDSUP-386: Elasticsearch: BAs are disabled on Search Screen.
The Index Management Tab will no longer be shown on SaaS v2 systems if the customer has multi-tenant endpoints or no Elasticsearch configurations. It will still appear on Elasticsearch configurations that were indexed to single tenant.
This supersedes 2024.4-2024-12-11-15-30-10 and earlier versions.
Hotfix HOTFIX-7973 doesn't have an approved description, yet. This is related to ISSUE-695212, ISSUE-698944, ISSUE-751881.
Fixed an issue in which the Save button was not clickable following the upload of a new asset via the Asset Representation component.
Fixed the problem in Web UI occurring when the Business Function chosen to filter out unnecessary suggestions for the Data Container used in the Unfolding Data Container view was not called, which caused all suggestions to be sown shown, even those not needed.
Hotfix HOTFIX-7986 doesn't have an approved description, yet. This is related to RDPORT-18116: Configuration LowMemoryDetector.HeapDumpDirectory : backporting fix.
Fixed the sorting order of attributes in Web UI in the Attribute Value Group header component after the reload of a screen. When attributes have a configured Display Sequence, then the Display Sequence is used for sorting order. Otherwise, the Title is used or ID (if Title is empty or two attributes have the same title).
Additional diagnostic data has been added to help diagnose the root cause of the problem where Proof View is throwing an internal error.
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 2024.4-2024-12-09-15-22-48 and earlier versions.
Fixed the healthcheck plugin "Softvalues with Dual Visibility" so that it does not fail with the exception "SnapshotTooOldException" when the number of rows in the softvalue table is large.
Now, it is not possible to set the user group as its own parent. Doing this created a data inconsistency.
The default number of ports for the Office Preview conversion has been decreased from 4 to 2 in order to decrease the memory usage of Libre Office processes.
Added additional server logging for bulk update to log the stack trace of the exception when an OptimisticLockException occurs during the bulk-update service.
When doing a search that returns more results than can be displayed, the total number of results reported could be higher than the actual number of results. This has been fixed.
Hotfix HOTFIX-7976 doesn't have an approved description, yet. This is related to ISSUE-746609.
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.
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).
It is possible to enable HTML escape for Save Search IDs on Advanced Search screen. To enable it, contact Stibo Systems Support. Also, when deleting a saved search on the same screen, a confirmation popup will have the saved search ID escaped all the time to prevent XSS vulnerability.
Fixed incorrect styling for missing object types icons in the Web UI Tree Navigator.
Fixed a memory leak related to a business function used during the numerous parallel web service invocations.
For multi-queue environments, we added the ability to serialize specific background process queues.
Fixed a problem where a NullPointerException could be thrown when importing an InDesign package via workbench.
This supersedes 2024.4-2024-12-06-09-57-44 and earlier versions.
For multi-queue environments, we added the ability to serialize specific background process queues.
Fixed a problem with BMEcat export, which was showing empty FVALUE tags.
BMEcat exporter now avoids incomplete asset references for non-existing asset sources.
Fixed a problem with Datasheet PDF creation where Calculated Attributes were not resolved for Pagination Rules and Validation Attributes.
When running on Cassandra, changing the dimension dependencies of assets could sometimes fail. This has been fixed.
Completed work to fix the healthcheck "Value links with dual visibility."
BMEcat exporter now avoids incomplete asset references for non-existing asset sources.
Fixed a problem with BMEcat export, which was showing empty FVALUE tags.
Fixed a problem in the exporter in which data container-inherited values for child-level nodes were not present in JSON outbound files.
Implemented a fix that avoids potential out of Memory errors when running the "Too many or too large revisions" health check.
Fixed a problem with missing clipping path images in a converted image when the output was set to create .tiff files.
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.
A fix has been made for a memory leak in the Web UI. Each time a Web UI configuration was changed, a little more heap memory was used to cache Web UI information because the old information was never deleted. This has been changed, so that when a user saves a Web UI configuration the cache is cleared. It is possible this fix can have the effect of slowing down the Web UI temporarily following a configuration save, but will return to normal once the cache is populated again.
Fixed a problem that occurred when conditional events from business conditions were not applied correctly on the Web UI's Multi Language Screens.
Fixed a problem that occurred when conditional events from business conditions were not applied correctly on the Web UI's Multi Language Screens.
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.
Fixed a problem that occurred when a "Missing unit" error thrown during Smartsheet validation was not shown for multi-valued attributes.
Fixed a memory leak related to a business function used during the numerous parallel web service invocations.
Fixed a problem with Datasheet PDF creation where Calculated Attributes were not resolved for Pagination Rules and Validation Attributes.
When running on Cassandra, changing the dimension dependencies of assets could sometimes fail. This has been fixed.
Fixed a problem with missing clipping path images in a converted image when the output was set to TIFF.
Hotfix HOTFIX-7949 doesn't have an approved description, yet. This is related to ISSUE-734430.
Fixed a problem that occurred when a "Missing unit" error thrown during Smartsheet validation was not shown for multi-valued attributes.
Fixed a problem in the exporter in which data container-inherited values for child-level nodes were not present in JSON outbound files.
Completed work to fix the healthcheck "Value links with dual visibility."
System properties for assets are now set even when the asset has no content.
This supersedes 2024.4-2024-12-06-07-49-02 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 2024.4-2024-12-04-15-06-32 and earlier versions.
The following problems have been fixed: - Now, a search button on a Search Panel will be enabled even if the "Allow Search for Blank" design mode parameter is not enabled for Value Search Criteria. - For Object Type criteria, a None label design mode parameter is correctly replacing the "-1" option in the object type list. - If the None label is not set for Object type criteria, a localizable "None" option will be shown instead of "-1".
The descriptions for the Add Data Container and Duplicate Data Container toolbar actions have been updated to state that these actions should only be used with the Globally Configured Multi Edit Data Container component (Multi Edit View in Global Representation). These components were specifically designed to be used in the above mentioned component, and should never be used outside of it.
Fixed an issue in which the Save button was not clickable following the upload of a new asset via the Asset Representation component.
HOTFIX-7955 was backported to to:automotive/7.0/automotive-7.0.52.spr (11.1-related automotive version).
Fixed a problem that occurred when the Node Picker form in Excel Smartsheets was not initialized correctly on Macs.
Fixed a problem that occurred when the Node Picker form in Excel Smartsheets was not initialized correctly on Macs.
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.
A code change was made to ensure node search behavior is the same between a search button click and pressing enter.
A code change was made to ensure node search behavior is the same between a search button click and pressing enter.
The following problems have been fixed: - Now, a search button on a Search Panel will be enabled even if the "Allow Search for Blank" design mode parameter is not enabled for Value Search Criteria. - For Object Type criteria, a None label design mode parameter is correctly replacing the "-1" option in the object type list. - If the None label is not set for Object type criteria, a localizable "None" option will be shown instead of "-1".
Added timeout to LoqateCloudEnhancedAddressQuality and LoqateCloudAddressQuality business rule plugins, with default set to 30 seconds. In order to change the timeout value, please contact Stibo Systems Support.
When upgrading indices from STEP 11.0 to the newer versions, the upgrade plugin will no longer look at the triggering workspaces assigned to the Elasticsearch configurations. From now on, it will upgrade all of them.
Hotfix HOTFIX-7936 doesn't have an approved description, yet. This is related to RDSUP-376: UI Search Screen Sorting - Sorting on Case GTIN does not work.
When upgrading indices from STEP 11.0 to the newer versions, the upgrade plugin will no longer look at the triggering workspaces assigned to the Elasticsearch configurations. From now on, it will upgrade all of them.
STEP was unavailable due to timeout issues. To fix the issue, a timeout was added for both the LoqateCloudEnhancedAddressQuality and LoqateCloudAddressQuality business rule plugins, with a default timeout set to 30 seconds.
This supersedes 2024.4-2024-12-03-15-46-58 and earlier versions.
An issue occurred that did not allow business rules configured as Run as Privileged to run in the Instrument UI. A code change has been implemented that corrects the issue.
An issue occurred that did not allow business rules configured as Run as Privileged to run in the Instrument UI. A code change has been implemented that corrects the issue.
This supersedes 2024.4-2024-12-02-14-36-31 and earlier versions.
Fixed an unexpected error on the Web UI Node Editor that occurred when evaluating business conditions. In cases where the attribute was both bound to the Data Container ISO date / ISO date-time attribute, and configured to display in the Web UI with the Enable Local Locale Formatting option setting activated in the Globally Configured Multi Edit Data Container component, the error occurred. This has been fixed.
Fixed an unexpected error on the Web UI Node Editor that occurred when evaluating business conditions. In cases where the attribute was both bound to the Data Container ISO date / ISO date-time attribute, and configured to display in the Web UI with the Enable Local Locale Formatting option setting activated in the Globally Configured Multi Edit Data Container component, the error occurred. This has been fixed.
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.
Fixed a problem occurring on Web UI Node List screens in which thumbnails displayed as larger than configured.
System properties for assets are now set even when the asset has no content.
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.
Fixed a problem in which a process designed to check for and remove invalid potential duplicates was throwing an exception when running in parallel matching.
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.
Fixed a problem in which a process designed to check for and remove invalid potential duplicates was throwing an exception when running in parallel matching.
Fixed a problem occurring on Web UI Node List screens in which thumbnails displayed as larger than configured.
An error prompted by a key error has been addressed so that the error notification is now more explanatory.
An error prompted by a key error has been addressed so that the error notification is now more explanatory.
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 2024.4-2024-11-26-14-15-15 and earlier versions.
There was an old behavior where it was possible to export translations when the source and the target were the same language, which has been removed. It is considered an invalid use case. However, the customer's setup relied on the old behavior and a solution was made to retain the old behavior on their systems. Any other customers with this same issue should contact Stibo Systems Support for details.
When doing a Lionbridge translation, the background processes in Quarantine state will no longer block for retranslation of an object.
When doing a Lionbridge translation, the background processes in Quarantine state will no longer block for retranslation of an object.
There was an old behavior where it was possible to export translations when the source and the target were the same language, which has been removed. It is considered an invalid use case. However, the customer's setup relied on the old behavior and a solution was made to retain the old behavior on their systems. Any other customers with this same issue should contact Stibo Systems Support for details.