2023.4 - 7.0.58 Release Notes
Release: December 2023
Bugfixes
TecDoc
Fixed an issue where the TecDoc Reference Data Import workflow did not consider TAF table 125.dat.
This problem resulted in inaccuracies in the allocation of valid Engine numbers to vehicle types. The TecDoc Reference Data import workflow now accurately considers TAF table 125.
This solution includes two hotfixes applicable to STEP versions STEP 10.3 MP5 + Automotive-7.0.45, STEP 11.0 MP3 + Automotive-7.0.48, STEP 11.1 MP2 + Automotive-7.0.52, STEP 2023.2 (11.2) + Automotive-7.0.53, and STEP 2023.3 (11.3) + Automotive-7.0.56.
Hotfix recipe: to:hotfix/663/issue-663734-HOTFIX-6917.spr
Hotfix recipe: to:hotfix/665/issue-665732-HOTFIX-6926.spr
Fixed NPE generated when calculating the size of the TecDoc imported files to report the import progress
Fixed a Null Pointer Exception (NPE) generated during the calculation of the size of TecDoc imported files, specifically when the file was empty or null. The bug fix addresses the NullPointerException in the calculateWeight function.
Hotfix recipe compatible with STEP 2023.3 (11.3) + Automotive-7.0.56: to:hotfix/657/issue-657088-HOTFIX-6870.spr.
Hotfix recipe compatible with STEP 10.3 MP4+ Automotive-7.0.45: to:hotfix/657/issue-657088-HOTFIX-6870.spr.
Resolved an issue where the TecDoc Supplier Data importer created application records (linkage) with two referenced Generic Articles
Resolved an issue in which the importer failed to establish a local reference to the Generic Article for specific TAF table 400 entries. This problem resulted in inherited multiple references in the linkage, leading to errors in displaying Supplier Articles in the Web UI. The fix ensures adherence to the solution's restriction of one reference to a Generic Article for a linkage, preventing duplicates.
Resolved an issue where incorrect asset references were generated in the TecDoc Supplier Data import
The TecDoc Supplier Data importer now accurately considers reference replacements for digital assets, specifically for 'TD_SupplierArticleToResource' reference type. Previously, references between supplier articles, accessory list members, part numbers, part lists, and digital assets / logos were accumulated for each import but not replaced. With this fix, asset references on the product will be correctly replaced with each new import run, ensuring the handling of 'Supplier Article To Resource' references.
Additionally, an issue consisting of a duplicate replacement rule for 'TD_SupplierArticleToAccessoryList' reference has also been addressed.
Correction of outdated PCdb codes in PIES version 7.2 exports
Resolved an issue where outdated PCdb codes were used in PIES version 7.2 exports. The AutoCare standard previously rejected the 'ASM' code during validation, leading to the error message "12674 Invalid Code(s): ASM is not currently an official PCdb Code for C10 Application Summary Brand AAIAID: BCNB." This problem has been resolved.
Hotfix recipe compatible with STEP 10.3 MP4+ Automotive-7.0.45: to:hotfix/660/issue-660176-HOTFIX-6894.spr.
Patch Recipe
For SaaS environments, upgrades can be done in the SaaS Self-Service UI or (if not available) by raising a request with Stibo Systems Support. More information on the upgrade process in the SaaS Self-Service UI can be found in the Upgrade Environment section in the in-build User Guide.
For on-premises customers, the Automotive add-on component and STEP baseline can be installed using these commands:
to:automotive/7.0/automotive-7.0.58.spr
The above recipe is compatible with the following STEP 2023.4 baseline recipe:
to:step/platform/step-2023.4.spr
Important: Once an Automotive add-on is installed to a base STEP system, the base system cannot be upgraded without upgrading the Automotive add-on at the same time. Additionally, when upgrading any base STEP system that has any Automotive add-on installed, both install recipes must be prepared at the same time.
For on-prem systems, refer to the SPOT Program documentation for more information, including how to use the SPOT --upgrade command to also find compatible components that can be added at the same time as the baseline patch (--upgrade=all) in the SPOT Program topic of the System Administration Guide found in Downloadable Documentation. For assistance, contact Stibo Systems Technical Services.
For customers that have custom add-on components and/or if Stibo Systems Support is deploying your system upgrades and patches, submit an upgrade request via the Stibo Systems Service Portal.