Every so often changes are made to the LubeSoft system that will affect how vehicle data is saved at the store. These changes can include new data fields or YMME definition changes. When a store updates to a version that has one of these changes and shares to a store that has not updated there is the possibility that pieces of vehicle data will be lost or invalidated. To prevent this from happening on a large scale we have implemented version validation for each National Vehicle Sharing Group. Currently we keep track of the version number for the isi-database, isi-esm, and isi-lubesoft-sharing system packages.
A maximum version is stored for a National Vehicle Sharing Group. Before each vehicle incremental load is generated, each nightly changes download attempt, and before every merge request store locations will check their currently installed versions against the versions saved for their National Vehicle Sharing Group. Real-time snapshot downloads will not be prevented.
If the store’s versions are less than the group’s versions the vehicle sharing process will fail. If the store’s versions match the group’s versions then everything continues as normal. If the store’s versions are greater than the groups versions, then the group’s versions will be updated to the store’s versions.
If one store in a group updates before other stores then the updated store will continue to push vehicle changes to ISI Central while ISI Central vehicle sharing will be blocked for the other store’s. As each store in the group updates to the new version they will start sharing vehicle information again and will download any changes that they missed previously.