| Table of Contents |
|---|
Setup Checklist
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
1. POS |
|---|
Infrastructure Task 2 -
| Status | ||||
|---|---|---|---|---|
|
| title | Example of Infrastructure Task |
|---|
Tasks | ||||||
|---|---|---|---|---|---|---|
|
| Expand | ||
|---|---|---|
| ||
Products that need age ranges assigned are created in POS and have age ranges added to POS |
| Status | ||||
|---|---|---|---|---|
|
2. INFRASTRUCTURE TASKS
|
|
2. |
|---|
Commerce Task 3 -
| Status | ||||
|---|---|---|---|---|
|
| title | Example of Commerce Task |
|---|
Commerce Tasks | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Ensure that the products to which you are assigning validated prompt(s) are set up in Aspenware Commerce.
|
|
Language String, Setting, HTML widget, etc. Task 4 -
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Ensure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time -
|
| Status | ||||
|---|---|---|---|---|
|
|
| title | Example of Configuration Task |
|---|
|
|
|
If using location in RTP, location code is entered
| Status | ||||
|---|---|---|---|---|
|
If multi day product, number of days is defined
| Status | ||||
|---|---|---|---|---|
|
If using non default lock time of 900 seconds, the desired lock time is configured.
| Status | ||||
|---|---|---|---|---|
|
|
Prerequisite Tasks
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
POS Tasks
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
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
Configure Regular (Non-SheerID) Validated Prompts
Step 2 Header
1. Configuring Regular (Non-SheerID) Validated Prompts
When a customer checks out with a product or product plus attribute value that is set up with validation prompt restrictions, they will see a verification section on the Personalization step of checkout. The customer will be unable to continue past Personalization until they enter a valid verification code. A code can only be applied a single time on the Personalization step and cannot be used for multiple household members in the same order unless it's set up as a “Validate On Checkout Assignment” prompt. If in RTP|One it is set up for more than one-time use, it can be used again for subsequent orders.
A validated prompt can either be set up as a “Validate On Checkout Assignment” prompt for prompts that check guest eligibility or require a code entry that is checked on the Personalization step, a check is performed to ensure the code is valid and not expired. If a validated prompt is set up as a single-time use in RTP|One, then once the customer checks out for their order, the code is marked as used and cannot be applied a second time if it is set up for one-time use. Codes can be multi-time use or single-time use.
Product Prompts in Aspenware Commerce can be set to “Validate On Checkout Assignment”. If a product is assigned to a validated prompt that is set up this way, it takes the legwork away from the guest needing to enter a code and rather only allows “eligible” guests to be assigned.
Note: Stored procedure updates in RTP must take place in order for the validations to take place. Please email ski-support@aspenware.com to set these up in advance of configuring these prompts in Nopcommerce.
...
From the Aspenware Commerce Plugins>Product Prompts page in Admin, select to add a new prompt
Enter the following details
...
Text - Prompt text (visible to customers)
...
Code - RTP prompt code
...
Prompt type - set to Text string
...
Update/create stored procedure updates in RTP|One. This is required in order for the validations to take place.
Aspenware has created this RTP|One Guide as a starting place for RTP|One customer stored procedure set up: https://aspenware.atlassian.net/wiki/spaces/AE/pages/1347977269/RTP+One+Guide+Validated+Prompt+Setup?moved=true
HINT: Email ski-support@aspenware.com for help gathering requirements and creating custom stored procedures in advance of configuring these prompts in Aspenware Commerce. When emailing support, provide answers to the following form of questions:
Requirements Summary: Explain the business requirements you are trying to accomplish through this product to the best of your ability
Is this transferrable? Does the customer need to be validated?
What are you expecting this prompt to be validating off of?
If Voucher… (Consider using Voucher functionality)
Provide Template id
Provide Type
Answer: Does the SKU added to the cart need to match the product header added to the voucher?
If General Program Profile
Provide GPP id
Provide rules for how customers are assigned GPPs in RTP
If the desire is to create a new table of data /codes to validate off of
Provide details on the types of codes that will be created and validated off of
Provide whether code will be single-time use or unlimited use code. Unless using vouchers, cannot be several-time use code. Can either be 1 time or unlimited valid for a period of time
Do you want to allow the same code to be entered more than once in the same transaction, or be limited to 1 entry.
Product
Provide a product or component that you expect a customer to have on their profile to validate against.
Access Profile
Provide an access profile that you expect a customer to have on their profile to validate against.
Other?
Provide details
Product header code: Pre-build the product in RTP and provide the product header code
Aspenware Commerce Product Link: Pre-build the product in Aspenware Commerce and provide the product link
Obtain RTP|One prompt code(s) for use in Aspenware Commerce configuration.
Commerce Tasks
Ensure that the products to which you are assigning validated prompt(s) are set up in Aspenware Commerce
Detailed Setup Guide
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Configure Regular (Non-SheerID) Validated Prompts
Assign Prompt to Product
1. Configure Regular (Non-SheerID) Validated Prompts
Go to Aspenware Commerce > Product Prompts in Admin.
Select Add Product Prompt and enter the following details:
Text: Prompt text (what you want to be visible to customers.)
Code: RTP|One prompt code.
Prompt type: Select ‘String’
Validate On Checkout Assignment: Check if the prompt in RTP|One is set up to check valid customer assignments. Do not check if the guest should enter a code.
Is Validation prompt
...
: Check
Is Required
...
: Check
Prevent Duplicates
...
: This disables the ability to use the same prompt value again within the same transaction. Recommended for single-use vouchers.
Click Add
...
.
...
2. Assign Prompt to Product
Return to the Product Prompts page.
Click View Assigned Product Prompts
...
.
Click Add Product Prompt Assignment.
Choose the desired product from the list of products.
From the Product Attribute drop-down, select All if the same validation prompt applies to the entire product, or if a validation prompt should only be assigned to one attribute selection, select the attribute to assign the prompt to.
Select the Product Prompt you just created in the previous section.
Click Add.
...
Insert excerpt