Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
Panel
panelIconId2601
panelIcon:cloud:
panelIconText☁️
bgColor#57D9A3

For Cloud UI Customers: Be sure to check out the NEW Look and Feel of Assignment on the PDP that is now available on the Refreshed PDP that is now available for Cloud customers!

Setup Checklist

Insert excerpt
DB:Set-up ChecklistDB:
Set-up Checklist
nopaneltrue

1. POS

TASKS

POS Task 1

Status
colourRed
titleRequired

Expand
titleExample of POS Task
Products that need age ranges assigned

Tasks

Products that require assignment are created in POS and require assignment and possibly have age ranges added to POS -

Status
colour

YellowInfrastructure Task 2 -

Red
title

Prerequisite

2. INFRASTRUCTURE TASKS

Required

Status
colour

Red

Yellow
title

Required Expand
titleExample of Infrastructure Task
​Confirm that the Azure function app is setup and configured to the desired frequency.

Prerequisite

2. Aspenware Commerce Tasks

Products that require assignment are created in Aspenware Commerce and attributes are finalized -

Status
colourRed
titleRequired

Status
colourYellow
titlePrerequisite

3. COMMERCE TASKS

Commerce Task 3 - StatuscolourRedtitleRequired

Expand
titleExample of Commerce Task

Confirm that the

Aspenware Commerce

products that will have

inventory

Requires Assignment assigned to them are

fully configured

set up with the

correct attributes -

Age Rules if necessary.

Status
colour

Red

Blue
title

Required

optional

Status
colourYellow
titlePrerequisite

Language String, Setting, HTML widget, etc. Task 4 -

Update relevant 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.

Status
colour

Blue

Yellow
title

optional Expand
titleExample of Setting Task
​Ensure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time

Prerequisite

Update Content Blocks on Assignment step of checkout via HTML Widgets -

Status
colour

Blue

Red
title

optional

Required

Status
colourYellow
titlePrerequisite

Configuration Task 5 -

Ensure Requires Assignment Product Classification is set up at the product level.

Status
colourRed
titleRequired

expand

  • Do not add to category only level or at the product attribute level

Status
colourGreen
title

Example of Configuration TaskInventory is mapped to product or product variant in the Inventory Pool plugin

Detailed Setup

Configure the Assigned to attribute on the PDP

Status
colour

Red

Blue
title

RequiredCode is entered

Optional

Status
colour

Red

Green
title

RequiredIf using location in RTP, location code is entered

Detailed Setup

Configure Add-On Product to Require Separate Assignee than Core Product

Status
colour

Red

Blue
title

RequiredIf multi day product, number of days is defined

Optional

Status
colour

Red

Green
title

RequiredIf using non default lock time of 900 seconds, the desired lock time is configured.

Detailed Setup

Configure “Fenced” Assignment through Assignment Validated Prompt

Status
colourBlue
title

optional

Optional

Status
colourGreen
titleDetailed Setup

Prerequisite Tasks

Insert excerpt
DB:Prerequisites Tasks ExcerptDB:
Prerequisites Tasks Excerpt
nopaneltrue

1. 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 first

  • 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

Insert excerpt
DB:Setting, Language String and/or HTML Widgets for this featureDB:
Setting, Language String and/or HTML Widgets for this feature
nopaneltrue

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
titleExample 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:

    1. Calculate from Trip Start (this age range type is likely already configured), or 

    2. Calculate from Today’s Date (age range based on purchase date), or

    3. 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.

Info

Note: When possible use notes, warnings, and hints within info panel macros. See https://aspenware.atlassian.net/wiki/pages/resumedraft.action?draftId=781156460 for more details on these.

2. Step 2 Header

  • 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.

To add the feature terms to the Glossary, navigate to the glossary and add a header for your feature using an H2. Select the + and then select …view more. Search for Excerpt Include and in the Page Containing the Excerpt search for “Configuration: [FEATURE]” select to hide panel, preview and add.

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

Real Example of this page can be found here: https://aspenware.atlassian.net/wiki/spaces/DB/pages/edit-v2/1037172926

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.

    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.

NOTE: For the Assignment text HTML widgets, the text between the code elements, i.e. <p> and </p> is configurable.

Detailed Setup Guide

Insert excerpt
Detailed Setup Guide Excerpt
Detailed Setup Guide Excerpt
nopaneltrue

  1. Configure Product to Require Assignment in Checkout

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

  3. (Optional) Configure Rule to Prevent Duplicate Assignment for Similar Product Categories

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

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

Info

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.

Info

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.

Note

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.

Info

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

  • Unlimited Pass

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

  • Lift Ticket

  • 50% off Buddy Ticket

  • Add on Lift ticket purchased with Lesson

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

  • Ski Rental

  • Snowboard Rental

  • Demo Rental

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

  • Private Lesson

  • Kid’s Group Lesson

  • Adult Group Lesson

A guest cannot assign the same person twice to ANY of the products with this classification if the products share the same start date.

  1. Go to Aspenware Commerce > Product Classifications > Add Assignment and select the Category containing the product requiring prevent duplicate assignment from the dropdown.

  2. Select the desired product from the Product dropdown. 

  3. (Optional) If preventing duplicate is specific to a particular attribute combination or add-on selection, check the desired product attributes or add on.

  4. In the Classification table, check ‘{Insert Desired LOB Here} - Prevent Duplicate Assignment’ in the Assign column.

    1. 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. 

  5. 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.

Info

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.

Info

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

    1. Text - Prompt text (will not be visible to customers if set to “Validate on Assignment”)

    2. Code - RTP prompt code (Get from Aspenware Representative)

    3. Prompt type - set to Text string

    4. Validate On Checkout Assignment - Check this. 

    5. Is Validation prompt - set to True

    6. Is Required - set to True

    7. Prevent Duplicates - this can be checked or unchecked

  • Click Add.

...


  1. Next, select View Assigned Product Prompts and click Add Product Prompt Assignment

  2. Choose the desired product from the Product dropdown.

  3. 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. 

  4. Click Add.

...

5. (Optional) Assignment on Confirmation Emails and Order History

The catalogsettings.hiddenattributes setting dictates whether assignment is displayed on the confirmation email and in Order History. See the Settings Library and search for the setting to learn more.

...