Validation
Validation functionality in the configurator helps ensuring a valid product can be configured and ordered. A configurator model (or preset) is validated in various areas of the platform, like load configuration, add-to-cart, proceed to checkout and place quote or order. The various validation types are described below
Section | Description |
Version validity | Check to see if the loaded configuration still has all nodes allowed based on the current used live model. |
Preset availability | Check to see if the preset is available to use in the condition, like a logged-in customer |
Preset assigned to package group | When configurable bundle packages are used in a business flow, this check validates if the retrieved preset is possible to load. |
Version validity
Version validity is used to ensure that a product configurator is working with the actual model. So when the configurator loads a previously designed product it checks if the version matches with the latest published version. So it compares the configuration against the latest one that is used when a new configuration is done. This might be relevant for situations in which products are updated with new options or removed options. In case of a removed option, this can be because this option is out of stock or not able to product anymore.
The configurator logic for handling version mismatches is as following:
Removed options will be reset to the default option of that type. E.g. a color that is not available anymore will be set to the first or default color option. A notice will show that the model is updated and options might have been changed.
Additional options will just be additionally loaded as in the new model. So the “saved model” is mapped into the new model. The defaults of those options will be set as if it is loading a new configurator.
When a previously saved configuration that is not valid anymore is added to the cart directly, a message will show that the design can’t be added to the cart
When a previously saved configuration is already in the cart and checkout is started, a notice will show and the checkout button will be disabled.
Preset availability
A preset can be made publicly available or restricted to certain use cases. Like for example a certain customer that is logged in or a timed period.
This is controlled via the Preset Availability personalization action. The configurator logic of handling preset availability is as following.
A restricted preset loaded into the configurator will not load and instead a 404 not found page is shown
Preset in configurable bundle package group
When a configurator works with sales packages or grouped configurator product packages, the configurator validates if the preset is part of the chosen package group.
An error notice shows when there’s a mismatch without further instructions. So it’s a rather technical notice since situations like this shouldn’t occur since it is caused by a data setup issue.
Last updated