Page Comparison

Setup Checklist

Prerequisite Tasks

POS Tasks

• POS Task that must be completed first

Infrastructure Tasks

• Infrastructure Task that must be completed first. Remove section if not required

Commerce Tasks

• AW Commerce task that must be completed firstIf 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

Settings

• AW Commerce Settings that must first be completed

Language Strings

• AW Commerce Language Strings that must first be completed

HTML Widgets

• AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

1. Step 1 Header

2. Step 2 Header

1. Step 1 Header

• First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

  1. Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.

     1. Sub-bullet for step a. Include screenshots of the step and use skitch to mark up screenshots. It can be downloaded here: https://www.techspot.com/downloads/5705-skitch.html

Expand
title Example of content within a section
From the Aspenware Commerce Plugins>Age Range page in Admin, click View Add Range Types in the upper right corner. Click Add Age Range Type. Enter a name and description for the age range type. To set the date used to compare the customer’s age to the required age range, select: Calculate from Trip Start (this age range type is likely already configured), or  Calculate from Today’s Date (age range based on purchase date), or Specify the Calculation Start Date; the customer’s age on this date will be used to determine if they are eligible for the product based on the age ranges Click Add. Age Range Types can be edited and inactivated, but they cannot be hard deleted without contacting Aspenware.  Age Range types that are set to Calculate from Trip Start or Today’s Date will never need to be edited, unless you would like to edit the name. Age Range Types that are calculated from a fixed date however, will need to be edited each year to adjust for the current year. Image Removed   Hint: Age Range Types should also be adjusted year over year. If age ranges are calculated based on Trip Start, then they will not need to be updated. Once completed for all required age range types move on to create Age Range.

...

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.

  1. Title: Explain Assignment Limitations - New Group Member

     Image Added

  2. Title: Explain Assignment Limitations - Assignment Page

     Image Added

  3. See the documentation on editing these HTML widgets.

Detailed Setup Guide

1. Configure Product to Require Assignment in Checkout

2. (Optional) Configure Product to Offer Assignment Option on PDP

3. (Optional) Configure Add-On Product to Require Separate Assignee than Core Product

4. (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.

• 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

  1. Sub-bullet for step 1

     1. Sub-bullet for step a

...

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

How-to Guide of this page can be found here: /wiki/spaces/DB/pages/1040089511

...

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.