Change Logs are accessible from within the Stibo Systems Service Portal. To view the logs, log in and go to the 'Update Information' dashboard. Change Logs are linked under each update version (for all supported versions of STEP). SaaS users will also be able to access these Change Logs via the STEP Documentation that is accessible from their system's Start Page or from within workbench.
Note: Customers may want to search Stibo Systems Service Portal for their Issue Numbers (if shown). To do so, while in the Stibo Systems Service Portal, navigate to Issues (in the header bar) and then select 'Search for Issues.' Click on the 'Advanced' option on the filtering bar, and then type in 'issue=' and the issue number. Press Enter or click the magnifying glass icon to run the query. Users can only view Stibo Systems Service Portal issues for issue numbers that they have privileges to access. If the issue is not applicable to the user searching, then a 'No issues were found to match your search' message displays.
Component and Other Fixes
This list covers fixes that were made outside of regular projects / customer issues and components that were updated after 2024.3 was originally made available and prior to or with the 2024.4 update. Refer to the 2024.3 Change Log for fixes that went into the 2024.4 update. Also, refer to the 2024.4 Change Log for fixes that go into 2024.4 after the original update is made available.
Font change on Web UI Homepage
The title on the Web UI Homepage is now san serif and consistent with the other headers throughout the UI.
Fix for special character tag error on ECA editor
Fixed displaying of STEP tags in the eclass-advanced editor component. (component: eclass-advanced)
Fix for Async Translation is not working after upgrade to latest 2024.2
Fixed with HOTFIX-7805; Making sure there is no error when missing information about pending file count, or when this information is wrongly set to null. (component: async-translation)
Fix for search not working post upgrade to 2024.2
After the fix, upgrade of Elasticsearch configurations when migrating from STEP 11.0 or lower should pass without any errors and the upgraded Elasticsearch indices should behave as expected. (component: elasticsearch-integration)
When deduplication of events was enabled and an event was read by a business rule, future similar events could get removed, even though the associated data change had not been seen. This has been fixed. (components: local-loqate, inmemory, and elasticsearch-integration)
Fix for issue with PDX Channel Publish in pre-prod environments
Error handling of PDX channel configuration creation has been improved when STEP does not have an XML asset object type configured. (component: pdx-channel)
Fix for STEP Upgrade: PLM Compare function - missing values of supplier
Fixed an issue with the PLM Compare function in that some supplier values were not being displayed. (component: private-label-food)
Fix for attribute-based Advanced Search is case sensitive for multiple entries
Now, In-Memory List Search will respect the case sensitivity search options. It means that the multiple values search on Web UI’s Advanced Search screen (which is treated as a list search) will be case insensitive with both In-Memory enabled or disabled. (component: inmemory)
Fix for when passing a data element business function to the organisation data element results in error
Fixed a ClassCastException that occurred when the user attempted to pass a Business Function Normalizer, which returns a Set<OrganizationName> to another Organization Name Normalizer of a Matching Algorithm Decision table. (component: partydatamatching)
Fix for when the getOrganizationName() method is not recognized when getting an Organisation Name object
Fixed a problem in which it was not possible to call getOrganizationName() of the Organization Name Normalizer result in the Matching Algorithm Decision table. (components: partydatamatching and dnb-integration)
Fix for Asynchronous Translation Service – multiple target languages
Created a new HOTFIX-7898 that fixes the way translation files are sent to SDL translation service when a customer configures async translation with multiple targets on a single configuration. (component: sdl)
Fix for match tuning score not matching scores given when comparing two records on algorithm
Fixed a transitivity problem that occurred when records compared via the Organization Name Matcher could return different results depending on a comparison order. The error was caused by a bug in the multi-token comparator, which incorrectly processed a missing token factor as a PAIRED result, even though it had not been paired at all. Additionally, this bug appeared only in the reverse direction, which also broke transitivity. (component: partydatamatching)
Fix for Asynchronous Job process
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. (Component: async-translation)
Performance Enhancements
Fix for Workflow Profiles extremely slow
Performance improvement for Workflow Profiles. It will have an impact for profiles with a lot of node states where the nodes have a large number of revisions. (component: inmemory)