Configuration: Waivers

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.

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

• The Authorization Type needs to be set up in RTP needs to be set up and you need to copy down the code and needs to be set to active, display online needs to be checked, a comment should be defined, age range should be set as 18-no maximum age, authorization text HTML should be configured, override security level set to 0.

• The authorization type needs to be assigned to the product component.

Infrastructure Tasks

• If lift access needs to be blocked before a waiver is signed, ask your AW rep about getting AW’s Auto-Hotlist product installed in your environment.

Commerce Tasks

• Products need to be created.

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.

Settings

Before setting up specific waivers, decide whether waivers should be stored to RTP | One at the time of signature, or when the order is completed and sent to RTP | One. If the waiver signature should be stored at the time of signature, set the following setting:

Go to Configuration > Settings. Search for WaiverSettings.SignWaiverDuringCheckOut and set to true.

If waiver signature should be stored at the time of order completion to RTP | One, set this setting to false. 

Language Strings

• REference new documentation the JEnni sent

HTML Widgets

• AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

1. Review Considerations Prior to Configuration

• Are you going to require e-signature on all waivers, just some, etc? (Can be configured at waiver level)

• Do you want to store waivers immediately on signing? (only configurable at store level)

• Do you offer resort charge? If so, set up resort charge waiver.  

• Do you offer direct to lift products, or DTL products, that require a credit card on file to purchase? If so, setup the required resort charge/credit card collection waiver. 

• Would your legal team accept consolidated waivers where all waivers are signed by a single user? 

• If a waiver is already valid for a user at the time of purchase, do you want to require guests to sign again? 

• Would any waivers be helpful to offer signature in my account for - could be signed by any guest not just those purchasing a product? 

2. Configuring New RTP|One Waiver (Release of Liability & Resort Charge)

1. Go to the Aspenware Commerce > Waivers.

2. Click Add Waiver to open the Add waiver page.

3. Fill in the following fields (Optional fields are marked with an asterisk here) 

   1. Title: Enter the title of the waiver

   2. RTP Authorization Type Code: This is the code from RTP | One.

   3. Collect CC Info: Check this box if setting up a waiver that enables resort charge functionality, meaning the guest can enter a credit card to add to their access card to pay for purchases at the resort. Resort charge functionality is currently only supported for Authorize.net and tokenized Payeezy.

   4. CC Agreement Required: Check this box if a product is required to have a resort charge. This feature is often used for direct to lift products that charge the guest automatically for every day of skiing. 

   5. E-Signature Required: Check this box to require the customer to type in the name of the assigned user before checking off the waiver checkbox during checkout.

   6. Display in My Account: Check this box if the waiver should be able to be signed within My Account.

   7. Consolidate Release: Check this box if you want to allow for a consolidated view of the waivers during the personalization step in the store. For more information about Consolidated Releases, please see Step 7 below.

   8. Validate Signature - FIXED!

      1. To require customers to always sign (or resign) do not check “validate signature” 

      2. To have Aspenware Commerce check RTP for an existing waiver profile and mark already-signed waivers as signed, check “validate signature” 

      3. If a waiver is already signed and this is turned on for a waiver, this is what the personalize waiver signing step will appear like for a guest with a valid authorization profile.

   9. Start Effective Date: To test, must be earlier than today’s date. Is this the effective date of the waiver?

   10. End Effective Date: -  to test, must be later than today’s date. When the waiver is no longer effective?

   11. Link Text: This text box is not used in configuration.

   12. 1Risk ID: If configuring a 1Risk waiver please see configuration instructions at 1Risk waiver setup configuration guide (INSERT LINK)

   13. Text area: Enter waiver HTML in this field. To enter HTML, go to Tools > Source Code in the editor. A Source Code text box will appear. Paste waiver HTML in the Source Code text box. Entering HTML in the standard text box, and not within the Source code editor, will not display the authorization details on the site correctly.

4. Click Save. 
   

3. Assigning Waivers to Products

1. Go to Aspenware Commerce > Waivers in Administration.

2. Click Assign Waiver to Products.
   

   

3. Select the waiver(s) that should be applied to each product from the Assigned Waiver drop-down(s). Each product can be assigned up to four waivers. If an add on product requires a separate waiver, then assign the add on product the desired waiver.

4. Waiver Signing in My Account (Optional)

For resorts on RTP | One, waivers can be signed in my account. Guests can log in to the ecommerce site, go to My Account, and sign waivers for themselves and other members of their household without being required to check out.

In the waiver plugin, waivers can be set to show in My Account by checking Display in My Account when editing a waiver. If a waiver is set to show in My Account, and is already signed by the household member, then the waiver will show as signed in My Account, but if the waiver is not yet signed, waivers can be signed here and will be recorded in RTP | One as Authorization type profiles for the designated guest. The following settings and language strings should be set up and edited to turn on the feature and to customize copy on the waiver signing screen in my account. 

5. Resort Charge in My Account

For resorts on RTP | One and have Authorize.net as a payment provider,  the resort charge feature can be set up for households in My Account. Guests can log in to the ecommerce site, go to My Account and set up resort charge for themselves and other members of their household without being required to check out.

In the waiver plugin, waivers can be set as “resort charge waivers” by checking both the Is Resort Charge Waiver and Collect CC Info settings when editing a waiver. If resort charge is already enabled for the household member, meaning they have both a primary credit card profile on their account or inherited to their account, and they have agreed to the resort charge authorization type,  then the household will be toggled on for resort charge and the configured credit card will be displayed for the household. 

The primary credit card set up for resort charge for the individual and household can be added and updated from this screen and RTP | One will be updated. If a household member is not set up for resort charge, they can be toggled on for resort charge. This will both add the primary credit card to their profile and add the resort charge authorization type agreement to their profile. The following settings and language strings should be set up and edited to turn on the feature and to customize the copy on the resort charge screen in my account. 

6. Activating/Inactivating Waivers to be Signed on Personalization Step

This setting will affect whether an authorization profile is created in RTP | One as soon as the waiver is signed (and prior to checkout/order processing). If using 1Risk waivers set this value to true (See Configuration Guide for 1Risk (INSERT LINK).)

1. Navigate to Aspenware Commerce > Settings. Search for WaiverSettings.SignWaiverDuringCheckOut

2. To ensure an authorization profile is created during the personalization step, select Edit and set the value to true.
   
   

   

7. Conolidate Waivers (Optional)

Waivers can be configured as eligible for consolidation. The default is false (which preserves existing functionality for all waivers). The administrator must enable Waiver Consolidation at the individual waiver level to turn on this feature. To mark a waiver as eligible for consolidation:

1. Go to Aspenware Commerce > Waivers.

2. On the Waivers page, find the waiver you wish to edit, and click Edit.
   

   

3. Select the checkbox under ‘Consolidate Releases’

   

4. Scroll to the bottom and click Save.
   

5. See the table below for examples of what a guest will see in the store if waivers are consolidated.

Description of Images associated with Consolidated Waivers	Image (Click to Expand)
When Consolidate Releases is checked for a waiver, any products that use that waiver will show in a consolidated view on the personalization step in the store, so the logged-in user will be able to sign all waivers for all members in the cart at one time. If there are any products in the cart which have waivers that are not eligible for consolidation, those waivers will behave as they did previously, where each member shows as an individual row on the personalization step, and each of those waivers must be signed for each member.
For the consolidated waivers, there is no signature box, as the signed-in user is signing for multiple participants.
The RTP|ONE Authorization Profile comment text shows the same information as it did previously for individually-signed waivers, with the signed-in user shown as ‘agreed for’ the other person.