Validation Validation logic determines the pre-requisites for a registrant to be able to proceed to the checkout, typically hosted in a Payment Service Provider, based on the contents of their basket. Validation may optionally be performed on individual catalog pages in a form, and/or at the end of a registration. In-form Validation Use in-form validation to implement immediate checks based on a current page. This can provide a more efficient registrant journey than delaying any validation until the final step. Frequently however, additional verification is needed at the point of checkout. See Basket Validation below. In the form editor, select one of the shop pages then navigate to Current Page Settings. The Require at registration controls the pre-requisites to advance beyond the current page; if the condition is not met, the next button is not available so the registrant is locked into the current page. Note this setting relates to an individual shop catalog instance on the form only. You can implement multiple shop catalog pages, each with its own requirements set. None means there are no specific requirements to advance beyond the current page. There’s no need to add anything to the basket. Note that shop products can be mandated to be in the basket based on their item properties. At least one product checks for there being a product of any type in the basket. Without one or more products, the registrant cannot proceed. At least one access product checks for a more specific product type being in the basket; an access product. Without one or more access products, the registrant cannot proceed. Basket Validation Prior to proceeding to the checkout (or generating an invoice for payment), use additional validation checks to confirm the basket meets the registration requirements. You can also use rules to add more advanced logic, for example different validation criteria based on properties of the registrant. In the case that the basket is not valid, the reason(s) are displayed to the registrant, so they can step back through the form to make the required changes to their selected shop product(s). Select +Add to create a new validation definition. You can create multiple conditions per order, however the order you create them in isn’t critical since all conditions must be met for the basket to be considered valid. Configure whether the condition applies to all visitors, all visitors where a configured rule is met, or all visitors where a configured rule is not met. Product Requirement Applicable to both generic and rule-based validations, product requirements specify the items which need to exist in the basket. For more complex scenarios, you can set up multiple validation rules, remembering that all need to be valid to progress to the basket checkout. Select Any product to confirm at least one product (of any type) is in the basket Select Access product to confirm at least one access product is in the basket Select Access product for areas where the an access product is needed for at least one of the assigned areas. To validate access products for multiple areas, add multiple validation rules each with its own area configured. Select Specific product to mandate a shop item in the basket. For this option a quantity is also mandated (the default is 1) Select Specific product any to mandate at least one of a number of different configured shop items int the basket Using Rules The product requirements can be enhanced by associating a rule, to check additional properties of the registration, event or system properties such as the current date. To suit different scenarios, you can choose whether the product requirement is needed when the applied rule is valid (so the condition(s) return ‘true’) or where the applied rule is invalid (so the condition(s) return ‘false’). When defining rules, you set up one or more conditions to check. You can combine these rules together using AND or OR logic, to control whether all rule conditions must apply or any of conditions. You can also reference other rules from your event’s rules library (nested rules) offering near limitless possibilities for conditional logic. For more information on Visit’s powerful rules feature, as used extensively throughout the platform, see the dedicated help pages.
