Setup Checklist
This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.
1. POS Tasks | |
|---|---|
Products that require assignment are created in POS and require assignment and possibly have age ranges added to POS - REQUIRED | PREREQUISITE |
2. Aspenware Commerce Tasks | |
Products that require assignment are created in Aspenware Commerce and attributes are finalized - REQUIRED | PREREQUISITE |
Confirm that the products that will have Requires Assignment assigned to them are set up with the Age Rules if necessary. OPTIONAL | PREREQUISITE |
Update relevant language strings
| PREREQUISITE |
Update Content Blocks on Assignment step of checkout via HTML Widgets - REQUIRED | PREREQUISITE |
Ensure Requires Assignment Product Classification is set up at the product level. REQUIRED
| DETAILED SETUP |
Configure the Assigned to attribute on the PDP OPTIONAL | DETAILED SETUP |
Configure Add-On Product to Require Separate Assignee than Core Product OPTIONAL | DETAILED SETUP |
Configure “Fenced” Assignment through Assignment Validated Prompt OPTIONAL | DETAILED SETUP |
Prerequisite Tasks
This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.
1. POS Tasks
If this product is sold onsite and the POS product requires assignment, and/or has age rules applied to it, confirm that the product requires assignment in the POS and that age ranges are set up.
2. Commerce Tasks
Confirm that the Aspenware Commerce products that will have requires assignment assigned to them are fully configured.
Confirm that the products that will have Requires Assignment assigned to them are set up with the Age Rules if necessary.
3. Settings, Language Strings and/or HTML Widgets for this Feature
This feature may require updates to the following settings, language strings and/or HTML Widgets. Learn more about how to update and create Settings, Language Strings, and HTML widgets follow the links to the respective section.
Language Strings for the Assignment Page
Language String | Default Text | Purpose |
|---|---|---|
account.login.checkout.assign.steptitle | Assign | This controls what displays in the checkout breadcrumb path for the “Assign” step. |
account.login.checkout.assign.title | Assign Products | This controls the page title in checkout for the “Assign” step. |
account.login.checkout.select.default | Select Group Member | This controls what displays in the assignment drop-down before a group member is selected. |
Language Strings for Eligibility Restrictions
Language String | Default Text | Trigger |
|---|---|---|
checkout.unassignable.agerestriction | Age restriction | Customer cannot be assigned because they are not of a valid age for that product. |
checkout.unassignable.fastflow | Fastflow | Customer cannot be assigned because the variant is a fast flow only option requiring that a customer be opted into fast flow to be assignment eligible. |
checkout.unassignable.mediarequired | Media required to assign | Customer cannot be assigned because the variant is a reload only option requiring that a customer have an active media to be assignment eligible. |
checkout.unassignable.missingbirthdate | Add birthdate to assign | Customer is not assignable because they do not have a birthdate defined. |
checkout.unassignable.restricteditem | Assigning to restricted item | The customer is not assignable beccause they are not eligible based on an assignment validation prompt. |
HTML Widgets
There are several content blocks that are displayed to the guest when creating family members and on the assign products step of checkout explaining that specific guests may not be selectable in the assignment drop-down due to an age rule or other limiting factors. These are managed via HTML widgets and can be customized.
Title: Explain Assignment Limitations - New Group Member
Title: Explain Assignment Limitations - Assignment Page
See the documentation on editing these HTML widgets.
NOTE: For the Assignment text HTML widgets, the text between the code elements, i.e. <p> and </p> is configurable.
Detailed Setup Guide
This section describes all required steps to set up the feature after prerequisite tasks have been completed.
Configure Product to Require Assignment in Checkout
(Optional) Configure Product to Offer Assignment Option on PDP
(Optional) Configure Rule to Prevent Duplicate Assignment for Similar Product Categories
(Optional) Configure Add-On Product to Require Separate Assignee than Core Product
(Optional) Configure “Fenced” Assignment through Assignment Validated Prompt
1. Configure Product to Require Assignment in Checkout
Products that require customer assignment must be flagged as requiring assignment. Both core and add-on products can be set up to require customer assignment. Typically, for a core product that has add-ons booked as part of the product “package,” the core product and add-on products are assigned to the same customer, so the assignment is only asked for on the core product, and it is inherited by the add-on products as well. This inheritance can be broken, however, and an add-on product can be set up to be assigned to a separate user when this configuration is desired (skip to section 3 below for configuration steps for setting up distinct customer assignment on add-on products.)
Go to Aspenware Commerce > Product Classifications. Click Add Assignment and choose both the Category containing the product requiring assignment from the Category dropdown and the desired product from the Product dropdown.
Do not check the associated attribute values.
NOTE: Assigning the 'Requires Assignment' Classification should only be done at the product level, not the category level or the attribute level.
In the Classification table, check the ‘Requires Assignment’ classification to Assign it to the product.
NOTE: The ‘Requires Assignment’ classification cannot be added to add-on products. Skip to section 3 below for configuration steps for setting up distinct customer assignment on add-on products.
Click Add.
2. (Optional) Configure Product to Offer Assignment Option on PDP
Products can be configured to display the household module to logged in guests, which can be used to assign household members to products, grouping the assigned products under their name in the cart prior to checkout.
Go to Catalog > Attributes > Product attribute and click Add New to create a new attribute if it doesn’t already exist.
Select the ‘AssignedTo’ attribute from the Attribute dropdown.
Enter ‘[Assigned To]’ in the Text prompt field.
Do not check Is Required.
Select the ‘Textbox’ Control Type.
The Display order does not impact this attribute, so set to 0 or the highest number in the sequence based on preference.
IMPORTANT: Do not add the ‘AssignedTo’ attribute to any time-based activity products that leverage quantity selection on the product detail page.
3. (Optional) Configure Rule to Prevent Duplicate Assignment for Similar Product Categories
Some products should not be purchased by same customer more than once. For example a customer shouldn’t buy themselves two unlimited passes for the same season, or two lift tickets for the same day. These products must be flagged with a prevent duplicate assignment classification within the Product Classifications plugin.
There should be multiple prevent duplicate assignment classifications for your different line of businesses.
NOTE: If you are missing a desired prevent duplicate assignment Product Classification. Talk to your Aspenware Representative.
Product Classification | Assigned Products (Examples) | Result |
|---|---|---|
Passes - Prevent Duplicate Assignment |
| A guest cannot assign the same person twice to ANY of the pass products with this classification. NOTE: if guests should be able to combine different pass types, such as a weekend and 4 pack, do not add this classification to “combinable passes” |
Tickets - Prevent Duplicate Assignment |
| A guest cannot assign the same person twice to ANY of the products with this classification if the products share the same start date. |
Rentals - Prevent Duplicate Assingment |
| A guest cannot assign the same person twice to ANY of the products with this classification if the products share the same start date. |
Lessons - Prevent Duplicate Assignment |
| A guest cannot assign the same person twice to ANY of the products with this classification if the products share the same start date. |
Go to Aspenware Commerce > Product Classifications > Add Assignment and select the Category containing the product requiring prevent duplicate assignment from the dropdown.
Select the desired product from the Product dropdown.
(Optional) If preventing duplicate is specific to a particular attribute combination or add-on selection, check the desired product attributes or add on.
In the Classification table, check ‘{Insert Desired LOB Here} - Prevent Duplicate Assignment’ in the Assign column.
As noted in the table above, there are distinct prevent duplicate assignment classifications for Passes, Tickets, Rentals, and Lessons. Assigning all ticket variations of products to Ticket Product - Prevent Duplicate Assignment will enable preventing someone from buying a full day ticket for themselves and then also signing up for a lesson with ticket on the same day.
Click Add.
4. (Optional) Configure Add-On Product to Require Separate Assignee than Core Product
An add-on product can be set up to be assigned to a separate guest from the core product assignment, use a “kids ski free add-on” as an example. In order for an add-on product to be assigned to a separate person from the core product, the add-on product must have the “Requires Add-On Assignment” product classification. When set up this way, guests who are uniquely assigned to the add-on product can be required to sign waivers, fill out profiles, meet age restrictions, and complete additional tasks that are necessary for that add-on product fulfillment.
Go to Aspenware Commerce > Product Classification > Add Assignment and choose both the Category containing the product requiring assignment, which is likely the ‘Add On’ Category, from the Category dropdown and the desired add-on product from the Product dropdown.
Do not check the associated attribute values.
NOTE: Assigning the 'Requires Add-On Assignment' Classification should only be done at the product level and should only be added to true Add-On products. It should not be set at the category level or the attribute level.
In the Classification table, check the ‘Requires Add-On Assignment’ classification to Assign it to the product.
NOTE: The ‘Requires Add-On Assignment’ classification cannot be added to core products. Go to section 1 above for configuration steps for setting up requires assignment on core products.
Click Add.
5. (Optional) Configure “Fenced” Assignment through Assignment Validated Prompt
A validated prompt can be used to fence special/discounted product purchases to only “eligible” members, and this eligibility is based on customized rules that are configured in an RTP|ONE validated prompt (this not currently supported for Sirisuware).
Validated prompts are typically used to enforce that a guest previously purchased product N. Some validated prompts require a guest to enter a code and click “Validate,” which “checks” their eligibility, but validated prompts that are set up to “Validate on Assignment” take the leg work away from the guest and check guest eligibility on the assignment of the product - only allowing eligible guests to be assigned. This eligibility fencing is supported for both Assignment on the PDP and Assignment in Checkout.
HINT: A validated prompt stored procedure must first be set up in RTP|ONE. This can restrict sales so only certain guests can purchase. Talk to your Aspenware Representative to set this up.
Ensure that setup from step 1 is completed for the “fenced” product prior to starting this configuration.
Go to Aspenware Commerce > Product Prompts and select Add a new prompt.
Enter the following details
Text - Prompt text (will not be visible to customers if set to “Validate on Assignment”)
Code - RTP prompt code (Get from Aspenware Representative)
Prompt type - set to Text string
Validate On Checkout Assignment - Check this.
Is Validation prompt - set to True
Is Required - set to True
Prevent Duplicates - this can be checked or unchecked
Click Add.
Next, select View Assigned Product Prompts and click Add Product Prompt Assignment
Choose the desired product from the Product dropdown.
From the Product Attribute drop-down select ‘All’ if the same validation prompt applies to the entire product, or if a validation prompt should only be assigned to one attribute selection, select the attribute to assign the prompt to.
Click Add.