Refresh Spec Data
What happens when spec refresh is triggered:
Basic dictionaries refresh:
The system begins by updating its local data with the most current properties from the latest price list. This update covers:
Vehicle model (including ID, Name, Code, Group, Type, Year, and Family Name).
Vehicle body (including ID, Name, and Code …).
Vehicle grade (including ID, Name, and Code ….).
Vehicle engine (including ID, Name, and Code ….).
Equipment, accessories, and options (including ID, Name, and Code …).
The system then attempts to renew vehicle images
Car configuration attempt
The system then attempts to construct a matching car configuration, prioritizing a complete match for price revision:
First, it tries to match based on engine, grade, body, options, exterior, and interior.
If a full match fails, it falls back to matching based on engine, grade, body, options.(only if car wasnt build in strict mode initially)
There is no logic about how prioritise price rows if there several similar specs with same body/engine/grade:
Price List Validation and Update:
If a matching car configuration is found within the latest price list for given revision, the system performs the following updates:
The local name of the car configuration is renewed.
The end item code of the car configuration is renewed.
Vehicle title
Vehicle body (including ID, Name, and Code …).
Vehicle grade (including ID, Name, and Code ….).
Vehicle engine (including ID, Name, and Code ….).