Table of Contents |
---|
Setup Checklist
...
Table of Contents |
---|
Setup Checklist
Insert excerpt | |||||||
---|---|---|---|---|---|---|---|
|
1. POS TASKS | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
POS Task 1
|
| |||||||||||||||||||||||||||||||||||||||||||||||
2. INFRASTRUCTURE TASKS | ||||||||||||||||||||||||||||||||||||||||||||||||
Infrastructure Task 2 -
|
| |||||||||||||||||||||||||||||||||||||||||||||||
3. COMMERCE TASKS | ||||||||||||||||||||||||||||||||||||||||||||||||
Commerce Task 3 -
|
| |||||||||||||||||||||||||||||||||||||||||||||||
Language String, Setting, HTML widget, etc. Task 4 -
Set up WaiverSettings.SignWaiverDuringCheckOut to either true or false depending on whether or the signature should be stored at the time of signing. |
| |||||||||||||||||||||||||||||||||||||||||||||||
Configuration Task 5 -
|
|
...
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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 firstThe 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, 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
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
...
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.
...
Info |
---|
NOTE: If a waiver is signed in My Account, it will always go to RTP | One on the signature. |
Language Strings
AW Commerce Language Strings that must first be completedREference new documentation the JEnni sent
HTML Widgets
AW Commerce HTML Widgets that must first be completed
...
2. Configuring New RTP | One Waiver (Release of Liability & Resort Charge)
Go to the Aspenware Commerce > Waivers.
Click Add Waiver to open the Add waiver page.
Fill in the following fields (Optional fields are marked with an asterisk here)
Title: Enter the title of the waiver
RTP Authorization Type Code: WHAT IS THIS? This is the code fromRTP | One.
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.
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.
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.
Display in My Account: Check this box if the waiver should be able to be signed within My Account. Full configuration guide for waivers in my account(ADD LINK)
Consolidate Release: If this box is checked, any products that use that waiver will show in a consolidated view on the personalization step in the store, so the guest who is logged-in 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. (See Figure A below.)
Validate Signature - DO NOT USE UNTIL FIX FOR CHECKING EXPIRATION DATE IN PLACEFIXED!
To require customers to always sign (or resign) do not check “validate signature”
To have Aspenware Commerce check RTP for an existing waiver profile and mark already-signed waivers as signed, check “validate signature”
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.
Start Effective Date: To test, must be earlier than today’s date. Is this the effective date of the waiver?
End Effective Date: - to test, must be later than today’s date. When the waiver is no longer effective?
Link Text: This text box is not used in configuration.
1Risk ID: If configuring a 1Risk waiver please see configuration instructions at 1Risk waiver setup configuration guide(INSERT LINK)
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.
Click Save.
...
Figure | Description of Screenshot Example | Screenshot (Click to expand.) |
---|---|---|
Figure A | This figure shows an example of what the guest will see if Consolidated Waivers has been checked in the | |
Figure B | This figure shows an example of a Release Form that requires a signature by the guest. | |
Figure C | This figure shows an example of a signed waiver that has been validated in RTP | One. |
...
3. Assigning Waivers to Products
Go to Aspenware Commerce > Waivers in Administration.
Click Assign Waiver to Products.
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.
...
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).)
Info |
---|
NOTE: This setting applies to all waivers (even if using both 1Risk and Aspenware Waivers.) |
Navigate to Aspenware Commerce > Settings. Search for WaiverSettings.SignWaiverDuringCheckOut
To ensure an authorization profile is created during the personalization step, select Edit and set the value to true.
...