Page Comparison

Setup Checklist

...

• AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

1. Step 1 HeaderConfigure Regular (Non-SheerID) Validated Prompts

2. Step 2 Header

1.

...

• First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

  1. Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.

     1. Sub-bullet for step a. Include screenshots of the step and use skitch to mark up screenshots. It can be downloaded here: https://www.techspot.com/downloads/5705-skitch.html

Expand
title Example of content within a section
From the Aspenware Commerce Plugins>Age Range page in Admin, click View Add Range Types in the upper right corner. Click Add Age Range Type. Enter a name and description for the age range type. To set the date used to compare the customer’s age to the required age range, select: Calculate from Trip Start (this age range type is likely already configured), or  Calculate from Today’s Date (age range based on purchase date), or Specify the Calculation Start Date; the customer’s age on this date will be used to determine if they are eligible for the product based on the age ranges Click Add. Age Range Types can be edited and inactivated, but they cannot be hard deleted without contacting Aspenware.  Age Range types that are set to Calculate from Trip Start or Today’s Date will never need to be edited, unless you would like to edit the name. Age Range Types that are calculated from a fixed date however, will need to be edited each year to adjust for the current year. Image Removed   Hint: Age Range Types should also be adjusted year over year. If age ranges are calculated based on Trip Start, then they will not need to be updated. Once completed for all required age range types move on to create Age Range.

2. Step 2 Header

First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

Sub-bullet for step 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. 

1. From the Aspenware Commerce Plugins>Product Prompts page in Admin, select to add a new prompt

2. Enter the following details

   1. Text - Prompt text (visible to customers)

   2. Code - RTP prompt code

   3. Prompt type - set to Text string

   4. Validate On Checkout Assignment - Check if prompt in RTP is setup to check valid customer assignment. Do not check if the guest should enter a code. 

   5. Is Validation prompt - set to True

   6. Is Required - set to True

   7. Prevent Duplicates - this disables the ability to use the same prompt value again within the same transaction.  Recommended for single use vouchers.  

3. Click Add

...

1. Next Click View Assigned Product Prompts and click Add Product Prompt Assignment

2. Choose the desired product from the list of products

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

4. Click Add

...

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

How-to Guide of this page can be found here: [Internal] Configuration page Setup Guide

Real Example of this page can be found here: https://aspenware.atlassian.net/wiki/spaces/DB/pages/edit-v2/1037172926

...