| Table of Contents |
|---|
Setup Checklist
...
Ensure a “Pickup on PUB” rule is created in RTP|One to allow media to print at PUBs. Ensure the “Pickup on PUB” rule is added to PHCs in RTP|One for which media can be printed at the PUB using the QR code presented in Arrival.
Determine if you will require a photo for printing pass media.
If photo is required before a guest can print their media, ensure pass media components OR product component rules are configured with the required image setting when needed.
If photo is not required before a guest can print their media, then opt to use the rule on the product component rather than pass media rule. To configure this, you can make a product component rule in RTP|One admin where the rule name and keyword is "IMAGEREQUIRED" and add that to components where you want to require a photo when they're sold to the guest. This is used if you want to require a photo on a component that is not a pass media component, while on a pass media component you can just check the "Image Required" box.
Ensure your product components require a Rental profile when needed. Aspenware requires that RTP|One configuration setup has a product component rule in RTP|One admin where the rule name and keyword is "RENTALPROFILEREQUIRED".
Ensure your product components require a Child Registration profile when needed. Aspenware requires that RTP|One configuration setup has a product component rule in RTP|One admin where the rule name and keyword is "CHILDREGPROFILEREQUIRED".
Infrastructure Tasks
Work with your Aspenware Representative to implement Identity and to create the Azure application services required for Arrival.
Detailed Arrival Setup Guide
The following steps will need to be completed in Arrival Adminitration. To access Arrival Administration, simply go to <arrival.yourresort.com>/admin.
Set Up Task Type
Set Up Tasks
Set Up Activities
Set Up Locations
Update Language Strings
Update Theme
Set Up Admin Users (Optional)
Configure Export List of Eligible Customers for Email (Optional)
Configure Report for Missing Profile (Optional)
Configure API Tab
Ensure Arrival QR Codes Are Aligned With Pick up Box Approach
Configure Collections Tab
...
Arrival comes pre-configured with task types. However, you can determine the validity duration for each of the task types (child registration, rental profile, photo, etc.) You can configure how new (based on UpdateDate in RTP|One) a profile must be in order for Arrival to recognize that the task has already been completed.
Navigate to Arrival Admin > Task Types.
Select the task you’d like to update.
Enter the Effective Days value. For example, if you set “Rental Profile” to 365 days, a guest will not have to complete a rental profile if they already have one that is less than 365 days old. They will be given the option to update their profile, if they wish.
...
Navigate to the Tasks tab in Arrival Admin.
To create a new task, do not check any of the existing tasks in the list and configure a new task by adding the following fields in the Add New Task area:
Name:This is the task name that will display to guests on the site.
Minimum Age: Optionally limit guests who should be prompted to complete this task based on their age. This defines the youngest age a guest could be to be prompted to complete this task if configured.
Maximum Age: Optionally limit guests who should be prompted to complete this task based on their age. This defines the oldest age a guest could be to be prompted to complete this task if configured.
Is Optional: Toggle FALSE to make this task required. For example, in an online location using the transaction-driven flow, you may want to set a task to optional since all guests may not be present when the head of household is checking in. For a physical location using the location-driven flow, you may want to set a task to required since all guests will need to complete the task prior to starting their activity.
Task Type: Choose from the four available task types (Waiver, Rental Profile, Photo, Child Registration)
If Task Type= Waiver, enter the following:
POS Waiver ID: Enter the corresponding authorization code from RTP|One.
Select to Consolidate Waiver: If activated, each required waiver will show in a consolidated view, so the logged-in user will be able to sign all waivers for all members in their family that require that specific waiver at one time. If there are any waivers that are not eligible for consolidation, those waivers will be presented for each member to sign separately.
One Day Waiver: If toggled on, this setting will always use the current date to determine validity. Arrival will check RTP|One for a corresponding authorization record. If one exists, Arrival will check if today’s date falls between the start and end effective dates of the waiver for that customer for that waiver in RTP|One. This setting should be used if the RTP|One product sets RTP waivers to be the product date as the start and end effective dates. This is a way to require a new waiver be signed for each product date. If used, validation date setup should match RTP|One authorization setup for the corresponding waiver.
If outside of the date range, Arrival will determine the guest does not have a valid waiver, and prompt the guest to sign a new waiver.
If inside the date range, Arrival will determine the guest does have a valid waiver, and will not prompt the guest to sign a new waiver.
IMPORTANT: Ensure there is not a mis-match of Validation Date configuration across Arrival and RTP|One Authorization configuration. A mismatch could result in guests being emailed that they have a waiver to complete that they have already signed, or vice versa.
Start Effective Date: This sets the start effective date for the waiver in RTP|One. The date the signed waiver is effective from.
IMPORTANT: Ensure there is not a mismatch of Start Effective Date configuration across Arrival, RTP|One Authorization configuration, and Commerce waiver configuration.
End Effective Date: This sets the end effective date for the waiver in RTP|One. The date the signed waiver is effective until.
IMPORTANT: Ensure there is not a mismatch of End Effective Date configuration across Arrival, RTP|One Authorization configuration, and Commerce waiver configuration.
Validation Date: This date is used to determine validity.
Arrival will check RTP|One for a corresponding authorization record. If one exists, Arrival will check if the Validation date set in Arrival falls between the start and end effective dates of the waiver for that customer for that waiver in RTP|One.
If outside of the date range, Arrival will determine the guest does not have a valid waiver, and prompt the guest to sign a new waiver.
If inside the date range, Arrival will determine the guest does have a valid waiver, and will not prompt the guest to sign a new waiver.
This field should be left blank if you toggle “Use today as validation date” on. Often resorts will set the validation date as the same as the "end effective date" for season long waivers.
IMPORTANT: Ensure there is not a mis-match of Validation Date configuration across Arrival and RTP|One Authorization configuration. A mismatch could result in guests being emailed that they have a waiver to complete that they have already signed, or vice versa. The arrival export, which determines the list of guests to email that have unsigned waivers to complete keys off the validation date setup on the waiver in RTP|One, while Arrival determines whether a waiver task is needed for a guest once they login to Arrival based on the validation date configured on the waiver task in Arrival.
Signer validation: At least one of the following must be configured, but can more than one or all can be set.
Enable Agree Checkbox: If checked, the guest will need to check to agree to the waiver and will be stored in RTP|One that the guest checked to agree to the waiver.
Enable Text Signature: If checked, the guest will need to type the name of the signed-in user, and it will be stored in RTP|One that the guest typed X name to agree to the waiver.
Enable Wet Signature: If checked, the guest can “ink” their signature, and the image of the signature will be stored in RTP|One. NOTE: This option requires RTP2016 or later.
Custom Comment:This field gives an option to populate the comment box in RTP|One’s Authorization profile. Can be used with tokens {Signer}, {SignedDate}, {BrowserName}, {BrowserVersion} to provide who signed, on what date, with what browser, and what browser version.
For waivers, the exact HTML that a guest sees through Arrival will be saved in the profile text in the authorization record in RTP|One.
Validation and effective dates are only considered and used with location-driven configurations since these flows do not require products sold on guest accounts. For transaction-driven configurations, RTP|One waiver validation will be determined in RTP|One. If RTP|One determines a waiver is required, the Arrival setup must also include the same waiver configured with the corresponding authorization code and dates in order for guests to complete the waiver in Arrival.
Select UPDATE TASK when complete.
...
3. Set Up Activities
...
Add Tasks to a New Activity
Go to the Activities tab in Arrival Admin.
In the Activities List section, click the checkbox next to the desired Activity.
Scroll down to the Link Tasks section.
Choose a Task: Click here and select a Task to add to this Activity.
Click LINK TASK to add the selected task to the Activity.
Multiple tasks can be added via the steps above, or a task can be removed here by clicking the red trash can icon next to the task.
...
Go to the Locations tab in Arrival Admin.
To create a new location, do not check any of the existing locations in the list and configure a new location by adding the following fields in the Add New Location area:
Location Name:This name will display to guests on the site. This name will also be included in the directory within the URL. A '-' will substitute any space in the location name. (e.g. If the location name is Ski School the url will be http://arrival.yourresort.com/ski-school )
Description: This isused for internal organization. This description will not display to guests.
Is Enabled: This is equivalent to “publishing” the location. When selected, guests will be able to navigate to the Location URL.
Is Default:When selected, this location will be your default location.
IMPORTANT: Only one Location can be configured as the default Location. This is the location that will be loaded for /home.
Is Edit Profile Location: When this is selected, this Location will be your “Edit Profile” location. This Location should be set up with a location-driven configuration. It is designed to allow guests to update tasks they have already completed. For example, you can configure rental profiles and child registration tasks at this Location to allow guests to update these profiles even after they have valid profiles. Guests will have the option to navigate to this “Edit Profile” Location after completing check-in from a Location using the POS transaction-driven configuration.
NOTE: This configuration is optional for your resort. A max of one Location can be configured as the Edit Profile location. On the POS location URL, the edit profile button will only appear once all “POS” tasks displayed have been completed for all family members.
Use POS Transactions (RTP):When this is selected, this Location will function based on RTP|One orders and transactions, driving tasks off of incomplete steps for orders for the household in RTP|One. If unselected, this Location will follow the location-driven configuration outlined in the Locations Overview section of this document above.
Check in Complete Text:This is the messaging the guest will see once the guest has completed all required steps for this Location.
NOTE: HTML is supported, but should be limited to the standard text where possible (H1, H2, H3, P, UL, LI). While image tags are supported, special precautions should be taken to avoid breaking the responsive nature of the site across devices.
Default Activity: The default activity is the activity used to create check-in tasks for this particular Location. For a POS transaction location, only tasks that are added to this default activity will be presented to the user, even if RTP|One is indicating that additional info is required. For example: If RTP|One is indicating that the guest requires waiver #999 but that waiver is not created as a task and assigned to the default activity, the user will not be asked to sign the waiver in Arrival.
POS Transaction (transaction-driven) Location: Only the default activity is used for check-in at this time. In a future version, additional linked activities can be used to generate tasks and the order of assigned activities does not matter. Regardless, one must be selected as default for Arrival to function properly.
Non-POS (location-driven) Location: Only the default activity is used for check-in at this time. All other linked activities are ignored. In the future, all Locations will offer guests the ability to check in for one or more activities.
Assign Activities:The default activity must also be assigned to the Location.
Select your Location and in the column on the right, select the drop-down under Link Activities.
Select the Activity to assign to the Location.
Click LINK ACTIVITY.
Future versions of Arrival will support multiple Activities per location.
Once complete, select UPDATE LOCATION.
Once a Location is added, select the checkbox next to the desired Location to view and/or edit the Location.
...
BLE Connect: This is only used for resorts that have BLE scanning activated at their resort. For more information about BLE scanning, see the BLE Scanning Documentation.
...
6. Update Theme
All sitewide theme settings are configured under the Theme Settings tab.
General
Logo URL: Add a URL to the image you’d like to display on the welcome screen. Typically this is an image of your resort’s logo. Image recommendation is 256 pixels wide. The height can vary based on the standard proportion of your logo. SVG file types are preferred, but PNG works as well.
Welcome Page Logo Width: This is used to adjust the size of your logo image.
Favicon Image URL:Add URL to the Favicon logo you would like to use.
Background Image: Add a URL to the image you’d like to display as your background image. Image recommendation is 1920x1080 pixels and 270 KB.
Overlay Welcome Background with dark gradient: This allows a gradient overlay on the background. Choose between dark, light, or none.
Show Application Title as Image:Select this to display an image as your application title. If this is deselected, the Title language string under Application Header will display.
Application Title Image URL:Add a URL to the image you’d like to display as your application title. This will only display if the Show Application Title as Image setting is selected. Can be used if your resort has a branding image for Arrival.
Welcome page Arrival Title Width:This is used to adjust the size of your Title image.
Fonts
Primary Font Color:Update the color of the font that is used on the site.
Primary Font Weight: Update the weight of the font used on the site.
Buttons
Primary Button Background color: Update the color used on primary buttons.
Primary Button Text Color:Update the color of the primary button text.
Secondary Button Background color:Updatecolor used on secondary buttons.
Secondary Button Text Color:Update the color of the secondary button text.
Footer
Background Color:Update the background color of the footer. Can be entered using RGB, HSL, or HEX values.
Footer Background Image:Add a URL to the image you’d like to display in the footer.
Background Opacity:Change the opacity of the footer gradient overlay.
Border Color:Update the color of the border used in the footer.
Text Color:Update the color of the font used in the footer.
Media Card
Sidebar:If a guest is on desktop view, the sidebar appears and can be configured with a background image or just a color.
Background Color: If using an image do not set a color.
Background URL: This is the background image on the application sidebar.
Background Opacity: If using a Background image, set the opacity on the application sidebar so that text can appear as legible.
...
API Access Keys: In order for a CRM to obtain guest information, you must provide them with an API key from this list. Copy and paste existing API keys to share with your CRM(s). If you click the red trash can icon, this will delete an existing API and would break any established connections your CRM has through that key.
Create API Token: This generates a unique API key to call the data Arrival has obtained from RTP|One. You can create multiple API keys if you need to share with multiple systems and want to keep the keys unique. To create an API Key:
Click CREATE API TOKEN.
Input a Token Nickname: ie: {CRM Name}
Click CREATE TOKEN.
API Default Settings: This is the defaulted information a CRM will obtain when they call the API IF the CRM has not specified specific parameters. The two sections here function the same as the Reporting Tab’s “Begin Date” and “End Date”.
Days Before Current Day: Defines the starting date the report will generate information based on the start date (product date) of an order/transaction in RTP|One. A max of 5 months in the past can be selected.
Days After Current Day: Defines the ending date the report will generate information based on the start date (product) of an order/transaction in RTP|One. Any date in the future can be selected.
...
After you have updated these two fields click UPDATE DEFAULT SETTINGS and if your CRM has not specified these parameters, the next time they call on Arrival’s API they will receive guest information based on this date range.
Available API Endpoints & Documentation: This section describes information on how to call the API and the parameters that can be specified.
...