Page Comparison

Setup Checklist

Prerequisite Tasks

1. POS

...

• 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

Tasks

• RTP|One Tasks

  • The Authorization Type needs to be set up in RTP|One and you need to copy down the code. It should be set to active, ‘Display Online’ needs to be checked, a comment should be defined, the ‘Age Range’ should be set as ‘18-no maximum age’, the authorization text HTML should be configured, and the override security level should be set to 0.

  • The Authorization Type needs to be assigned to the product component.

  • When a waiver is signed in 1Risk using the Aspenware Commerce Checkout flow configuration, it also creates an Authorization Profile in the guest’s Customer Manager Profile for the guest within RTP|One.
    [ADD IMAGE]

• Siriusware Tasks

  • The Liability Form needs to be set up in Siriusare and you need to copy down the ID. The expiration date should be set and copied down, and the minimum age to accept should be set at 18. Set Liability text and HTML to your preferences.
    

  • Image Added

    The Liability Form needs to be linked to the Siriusware item.

  • When a waiver is signed in 1Risk using the Aspenware Commerce Checkout flow configuration, it also creates a liability in the Guest Activity for the guest within Siriusware.
    

    Image Added

2. External System Tasks

• Configure waiver(s) in 1Risk. You need to copy down the waiver 1RiskID (provided by 1Risk) for each waiver.

• Copy down your resort’s 1Risk URL (provided by 1Risk).

3. Infrastructure Tasks

• RTP|One Tasks

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

4. Commerce Tasks

• Products need to be created in Aspenware Commerce. For help setting up products, see detailed instructions on setting up products.

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

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

• Before setting up specific waivers, there are several settings that are required to be set properly for 1Risk waiver integration to work. Go to Configuration > Settings. Search for the setting below and define the value according to the table below.
  

Detailed Setup Guide

1. Review Considerations Prior to Configuration

2. Configure New 1Risk Waiver within Aspenware Commerce

3. Assign 1Risk Waivers to Products

1. Review Considerations Prior to Configuration

1. Do you need to have a record of the waiver being signed in your POS (RTP or Siriusware), if yes, checkout waiver configuration is the best option. Follow steps 2 and 3 below.

2. If answer to 1 is ‘no,’ are you going to require waiver signature for all online orders with products that are assigned waivers? If so, set up waivers to require waiver completion as part of checkout. Follow steps 2 and 3 below.

3. If answer to 1 and 2 are ‘no,’ are you planning to offer waiver signature as an optional task for all online orders with products that are assigned waivers? If so, set up waivers to offer waiver completion as a CTA on the order confirmation email. Follow step 4 below.

2. Configure New 1Risk Waiver within Aspenware Commerce

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. This name will be visible to guests at checkout.

   2. POS Code, depending on the setting ‘waiversettings.1riskpos,’ one of the following fields will appear

      1. RTP Authorization Type Code: This is the code fromRTP|One (See prerequisite steps above).

      2. Siriusware Form ID: This is the ID of the Siriusware Liability form (See prerequisite steps above).

   3. Collect CC Info: Do not check - not supported for 1Risk

   4. CC Agreement Required: Do not check - not supported for 1Risk

   5. E-signature required: Do not check, not supported for 1Risk (Signing rules come from 1Risk config)

   6. Enable Agree Checkbox: Do not check, not supported for 1Risk (Signing rules come from 1Risk config)

   7. Enable Wet Signature: Do not check, not supported for 1Risk (Signing rules come from 1Risk config)

   8. Capture Waiver HTML: Do not check, not supported for 1Risk (Capture rules come from 1Risk config)

   9. Display in My Account: Do not check, not supported for 1Risk

   10. Consolidate Releases: Do not check, not supported for 1Risk

   11. Validate signature:

       • If RTP|One is your POS, check this box if you want Aspenware Commerce to check RTP|One for an existing waiver profile and mark already-signed waivers as 'signed.”

         1. To require customers to always sign (or resign) do not check Validate Signature. 

       • If Siriusware is your POS do not check, not supported for Siriusware.

   12. Start Effective Date: Enter the date that indicates when the release or waiver is valid. (To test this feature, the date must be earlier than today’s date.)

   13. End Effective Date: Enter the date that indicates when the release or waiver is no longer valid. Typically, this is set to the season end date. (To test this feature, the date must be later than today’s date.)

   14. Link Text: Leave blank, not applicable

   15. Custom Comment:

       • If RTP|One is your POS, options for custom comments include saving the Authorization Type Code {AuthTypeCode}, Signer Name {Signer}, Signed Date {SignedDate}, Browser Name {BrowserName}, and Brownser Version {BrowserVersion} Any words not in curly brackets will also show in the custom comments field. (See Figures A and B.)

       • If Siriusware - Leave blank, not applicable

   16. 1Risk ID: Define value provided by 1Risk for the 1RiskID of the waiver. (See prerequisite task above)

   17. Text area: Enter “Signed in 1Risk”

4. Click Save. 

Figure	Feature Description	Example (Click to Expand)
Figure A	Custom Comment: In RTP|One only, if there are entries in this field, custom comments will be viewable in the guest’s authorization profile as shown.	Image Added
Figure B	Custom Comment: This example shows the tokens entered in the Custom Comment field.	Image Added

3. Assign 1Risk Waivers to Products

1. Go to Aspenware Commerce > Waivers in Administration.

2. Click Assign Waiver to Products.

   Image Added

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.

...

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: [Internal] Configuration page Setup Guide

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