Configio Release - February 13th, 2023

Have more questions? Submit a request

Allow Age Constraints by Month

Admin user’s now have the ability to set an age constraint more granular than 1 year so that they can constrain participant ages by months as well as years

  • When adding a Constraints for Min Age or Max Age, a value can be entered in Year/Month


  • Once added the display will denote the same Year/Month format in the Admin Constraints and in the cart displays



Age Constraint Label Cushions

Admin user’s now have the ability to set a monthly cushion value that will be applied to age constraints 
Example: You are running a Camp that is displayed with constraints for 8 - 12 year olds, but you wish to allow a participant of 7 years 9 months OR up to 12 years and 3 months to register in the cart

  • When a Min Age or Max Age constraint is added, a new field will be displayed to allow the cushion in months for each constraint 


  • There are two Configurations:
    • "Default minimum age constraint label cushion in months"
    • "Default maximum age constraint label cushion in months"
    • The default value is '0' and will not alter the behavior of any existing constraint values
  • When creating a new product, the values set in the Configurations will be used to populate the cushion, and can be changed on a per product basis
  • These values are not displayed on syndicated products


Show dependent product counts in cart

When using the Dependent Product setting 'Max Purchase Quantity Per Primary Item', you can now enable cart users to see how many remaining purchase quantity are remaining to them

  • On the product Advanced tab in the Dependent Product section, there is a new setting for 'Show count in cart'
  • When Show count is cart is enabled, the dependent product page and Add-On manager will display 'X/Y Items remaining'
    • X = The value of the products Max purchase quantity per primary item minus the number of that product in cart or in completed orders 
    • Y = The value of the products Max purchase quantity per primary item  
  • This setting is not applied when the Dependent Product Search page is used

Product Sub-type

When managing a product, Admin’s can now enter a product sub-type that can be used in reporting and integrations.

  • There is a new system list for "Product Sub-Types"
  • On the product Advanced tab, there is a new field for Product Sub-Type that displays items from the list


  • There is a New configuration "Require selecting a product sub-type when saving a product"
    • if the configuration is set to require the product sub-type, an error message "product sub-type is required" will be displayed if no sub-type is enter on saving a product
  • The product sub-type setting is not available on syndicated products


Complex Registration Type improvements

Admins now have a simplified way to set up large numbers of complex registrations types and advanced rules

  • When managing Product Group Registration Types, an Admin can select between using Product (Legacy) or Registration Type rule logic
  • Only one logic type can be applied per Product Group; if any rule exists using one Rule Type, it must be deleted in order to switch rule types
  • A badge can now have more than one Registration Type assigned to it. This is an accumulation of Registration Types assigned to purchased products AND/OR admin direct assigned
  • When viewing a badge, the final reg types should be displayed in a Comma Separated list of each badge/Reg Type
  • Rule Processing by Registration Rule type:
    • Rules are processed in the order listed in the Advanced Rules modal
  • All rules will be processed, regardless if a previous rule matched (this is different from Product Rule logic)
  • Admin assigned registration types are applied to the rules.
  • If a rule replaces an admin assigned type, the admin assigned type(s) will not be displayed in reporting, badge details, etc.  However, Admin assigned types will be displayed in the badge edit registration type modal so it can be removed.
  • Rules are stackable. This means if rule 1 assigns a new registration type, rule 2 will use the new  Registration Type set by Rule 1 for following rules

Articles in this section

Was this article helpful?
0 out of 0 found this helpful