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 Tasls | |
|---|---|
Products that require assignment are created in POS and require assignment and possibly have age ranges added to POS - REQUIRED | PREREQUISITE |
2. 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 DETAILED SETUP |
Content Blocks on Assignment step of checkout are updated via HTML Widgets - REQUIRED | PREREQUISITE |
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.
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.
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.
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
Update ‘account.login.checkout.assign.steptitle’ if ‘Assign’ is not desired as the default.
Update ‘account.login.checkout.assign.title’ if ‘Assign Products’ is not desired as the default.
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
Configure Product to Require Assignment in Checkout
(Optional) Configure Product to Offer Assignment Option on PDP
(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 Classification > 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 Assign for the ‘Requires Assignment’ classification.
Click Add.
Optional Go to the product editor page and navigate to the Product Attribute tab. (Core Product Only)
Select the AssignedTo attribute, enter [Assigned To] in the Text prompt field, do not select Required, and 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. (Core Product Only)
Note: Do not add the AssignedTo attribute to any time-based activity products that leverage quantity selection on the product detail page.
2. (Optional) Configure Product to Offer Assignment Option on PDP
First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes
Sub-bullet for step 1
Sub-bullet for step a
3. (Optional) Configure Add-On Product to Require Separate Assignee than Core Product
4. (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.
Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.