Page Comparison

...

...

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.

• If using the “optional” 1Risk waiver configuration option, The ‘Requires 1Risk’ Product Classification must be added as a classification if not already set up as a product classification.

  1. To set the ‘1Risk Waiver in Email Confirm’ Product Classification up as a new classification go to Aspenware Commerce>Product Classifications and select Add Classification and define the following fields as follows

     1. Name: 1Risk Waiver in Email Confirm

     2. Description: Assign this classification to core products that will leverage optional 1Risk waiver signing in the confirmation email. Do not assign if product is assigned to 1Risk Waiver in the Waiver plugin.

     3. Select the checkbox for Requires 1Risk.

     4. Click Add.

Detailed Setup Guide

1. Review Considerations Prior to Configuration

2. Configure New 1Risk Waiver within Aspenware Commerce

3. Assign 1Risk Waivers to Products

4. (Optional) Configure 1Risk Waiver to be completed from a CTA on the order confirmation email

...

2. Configure New 1Risk Waiver within Aspenware Commerce

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

  1. Title: Enter the title of the waiver. This name will be visible to guests at checkout.

  2. POS Code, depending on which POS is selected in the 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. Is Resort Charge Waiver: Do not check, not supported for 1Risk.

  12. Validate signature: Do not check, not supported for 1Risk.

  13. 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.)

  14. 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.)

  15. Link Text: Leave blank, not applicable

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

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

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

• 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.
Figure B	Custom Comment: This example shows the tokens entered in the Custom Comment field.

3. Assign 1Risk 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.

...

Products can be set up to send guests a link to complete 1Risk waivers upon order completion within the order confirmation email. A 1Risk waiver link is sent to a guest in their order confirmation email if the guest has a product, or products, in their order that are set up to require waivers. 

• Go to Plugins > Product Classifications > Add Assignment and select the Category containing the product requiring 1Risk waiver signing from the dropdown.

• Select the desired product from the Product dropdown.

  • If waiver collection is specific to a particular attribute combination and does not apply to the entire product, check the desired product attributes.

• In the Classification table, Check the Assign checkbox for ‘1Risk Waiver Option in Email Confirm.’

• In the SKU field for Requires 1Risk Waiver classification, enter the 1RiskID from 1Risk (see prerequisite tasks).

• In the Value field for Requires 1Risk Waiver classification, enter the waiverFormid, which is the shorter string and is an integer. 

...

• Click Add.

• Assignments for Products to Require 1Risk Waiver can be removed by selecting Delete.

• To update text that appears in the confirmation email within the table where guests sign their waivers, go to the Configuration > Languages page in Admin, clickEdit in the English row.

• From the Edit Language details - English page, click to open the String Resources section.

• The following languages are related to waiver signing in the confirmation table. 
  

• Next, go to Content Management>Message Templates, and click Edit to edit the ‘OrderPlaced.CustomerNotification’ email template. 

• To edit the email HTML, go to Tools>Source Code and adjust the HTML from there in the Source code window. Paste the token '%Order.Waivers%' below into your HTML in the appropriate place.

...

• Configure settings specific to this feature by going to Configuration > Settings > All settings (advanced) and searching for the following settings:

  1. waiversettings.1riskemailapiendpoint is the endpoint that Aspenware calls to retrieve the proper URL from 1Risk that will be delivered in the email template

     1. Click Edit.

     2. Enter the value provided by 1Risk to your resort.

  2. waiversettings.1riskemailapisecret is the special value that gives access to the 1Risk resort waivers.

     1. Click Edit.

     2. Enter the value provided by 1Risk to your resort.
        

        

• Go to Aspenware Commerce > Waivers.

  1. Find the waiver you would like to add email to and click Edit.

  2. Scroll down to the 1Risk Waivers section and complete the following fields:

     1. Send waiver emails checkbox: Checking this box will enable the email feature.

     2. Minor Age textbox: Enter the age for which the waiver-signer is considered a minor and must be signed by a legal guardian (this should match the minor age set in your 1Risk admin tool). Note that If no age is entered, then all waivers will be considered adult waivers and therefore require emailing if the participant is not the logged-in user.

  3. Click Save.
     

     

• Customize feature-specific language strings in Configuration > Languages and click English.

  • Under String Resource, search for the following strings to configure:
    

...