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.
1. POS TASKS | |
---|---|
POS Task 1 REQUIRED | PREREQUISITE |
2. INFRASTRUCTURE TASKS | |
Infrastructure Task 2 - REQUIRED | PREREQUISITE |
3. COMMERCE TASKS | |
Commerce Task 3 - REQUIRED | PREREQUISITE |
Configuration Task 5 - REQUIRED | DETAILED SETUP |
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
Before administering in Arrival, refer to the Aspenware1Risk waiver documentation to set up waivers properly in RTP|One.
Be sure to obtain the RTP|One waiver ID (you will need it to configure below).
1Risk Tasks
Obtain the following from external waiver ID (this will be a specific URL to the waiver) from 1Risk.
Commerce Tasks (Optional)
Before administering in Arrival, refer to the Aspenware1Risk waiver documentation to set up waivers properly in both Aspenware Commerce (optional).
Arrival Tasks (Optional)
Before completing the 1Risk portion of your waiver task in Arrival, refer to the Arrival documentation on location, activity, and task to set up your Arrival flow properly.
Detailed Setup Guide
Once you have reached the point of setting up your waiver task in Arrival, there are four additional values you will have to set. To update these settings:
Go to Arrival Administration > General Tab and enter the following:
1Risk URL: Enter the URL provided to you by 1Risk and the same as what is set on other platforms (e.g. Commerce or Resort Tools).
1Risk secret: This is decided by you and given to 1Risk; use the same one across any platform on which you use 1Risk waivers (e.g. Aspenware Commerce or Resort Tools).
1Risk Date Format: Select your date format from the drop-down menu.
Point of Sale: Choose your point of sale system from the drop-down menu. Note that Aspenware Arrival currently only supports RTP|One.
Click UPDATE GENERAL SETTINGS.
Go to Arrival Administration > Task Tab
Fill in the fields as indicated:
Name: Enter the name of the waiver. This name will be visible to guests at checkout.
Minimum Age: Enter an integer. This is the minimum age for which the waiver is valid.
Maximum Age: Enter an integer. This is the minimum age for which the waiver is valid.
Task Optional: Toggle based on whether or not the waiver is optional. (Typically left untoggled for waivers.)
Task Type: Select ‘1Risk Waiver’ (additional fields will appear.)
POS Waiver ID: Leave blank.
External Waiver ID: Enter the waiver ID URL given to you by 1Risk.
Consolidate Waivers: Leave untoggled
One Day Waiver: Leave untoggled
Effective Date: Enter the date for which the waiver will be effective.
Expiration Date: Enter the date for which the waiver expires.
Validation Date: This is the date used for determining validity (age or effective range).
The three toggles can all be left untoggled as signatures are captured within the 1Risk iframe.
Custom Comments: Enter the custom comment that you would like to have stored in RTP|One. Once the aiver has been signed with a custom comment (included tokens), it would appear like this is RTP|One:
These are the tokens you can add to your custom comment:
{AuthTypeCode}
{Signer}
{Signed Date}
{BrowserName}
{BrowserVersion}
An example might be “Waiver {AuthTypeCode} was signed by {Signer} on {SignedDate} in 1Risk using {BrowserName} {BrowserVersion}”
Click UPDATE TASK.