| Table of Contents |
|---|
...
1. POS TASKS | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RTP|One Tasks
|
| ||||||||||||||||||
Siriusware Tasks
|
| ||||||||||||||||||
2. External System Tasks | |||||||||||||||||||
Configure waiver(s) in 1Risk -
|
| ||||||||||||||||||
Copy down your unique 1Risk URL (provided by 1Risk’s Bill Brouse (bbrouse@1risk.com))
|
| ||||||||||||||||||
3. Infrastructure Tasks | |||||||||||||||||||
|
| ||||||||||||||||||
4. Commerce Tasks | |||||||||||||||||||
Define Settings -
|
| ||||||||||||||||||
Install the Waivers plugin
|
| ||||||||||||||||||
Considerations Prior to Configuration (See Below) Products need to be created in Aspenware Commerce.
|
| ||||||||||||||||||
|
| ||||||||||||||||||
2. Configure New 1Risk Waiver in Aspenware commerce -
|
| ||||||||||||||||||
3. Assign Waivers to Products
|
| ||||||||||||||||||
4. Assign Optional Waiver Signing Step to Products |
|
...
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.
.png?version=1&modificationDate=1613596249894&cacheVersion=1&api=v2)
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.
.png?version=1&modificationDate=1613596246382&cacheVersion=1&api=v2)
...
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.
...
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)
Title: Enter the title of the waiver. This name will be visible to guests at checkout.
POS Code, depending on the setting ‘waiversettings.1riskpos,’ one of the following fields will appear
RTP Authorization Type Code: This is the code fromRTP|One (See prerequisite steps above).
Siriusware Form ID: This is the ID of the Siriusware Liability form (See prerequisite steps above).
Collect CC Info: Do not check - not supported for 1Risk
CC Agreement Required: Do not check - not supported for 1Risk
E-signature required: Do not check, not supported for 1Risk (Signing rules come from 1Risk config)
Enable Agree Checkbox: Do not check, not supported for 1Risk (Signing rules come from 1Risk config)
Enable Wet Signature: Do not check, not supported for 1Risk (Signing rules come from 1Risk config)
Capture Waiver HTML: Do not check, not supported for 1Risk (Capture rules come from 1Risk config)
Display in My Account: Do not check, not supported for 1Risk
Consolidate Releases: Do not check, not supported for 1Risk
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.”
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.
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.)
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.)
Link Text: Leave blank, not applicable
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
1Risk ID: Define value provided by 1Risk for the 1RiskID of the waiver. (See prerequisite task above)
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. | .png?version=3&modificationDate=1613598569076&cacheVersion=1&api=v2) |
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.
...