Table of Contents |
---|
Setup Checklist
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
1. POS TASKS | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
POS Task 1
| ||||||||||||||||||||||||
| ||||||||||||||||||||||||
Products that need age ranges assigned are created in POS and have age ranges added to POS |
Status | ||||
---|---|---|---|---|
|
2. INFRASTRUCTURE TASKS
Infrastructure Task 2 -
Status | ||||
---|---|---|---|---|
|
Status | |
---|---|
|
Status | ||||
---|---|---|---|---|
|
3. COMMERCE TASKS
Commerce Task 3 -
Status | ||||
---|---|---|---|---|
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Confirm that the Aspenware Commerce products that will have inventory assigned to them are fully configured with the correct attributes -
|
Status | ||||
---|---|---|---|---|
|
Language String, Setting, HTML widget, etc. Task 4 -
Status | ||||
---|---|---|---|---|
|
Status | |
---|---|
|
Status | ||||
---|---|---|---|---|
|
Inventory is mapped to product or product variant in the Inventory Pool plugin
Status | ||||
---|---|---|---|---|
|
Configuration Task 5 -
Status | ||||
---|---|---|---|---|
|
title | Example of Configuration Task |
---|
Status | ||||
---|---|---|---|---|
|
If using location in RTP, location code is entered
Status | ||||
---|---|---|---|---|
|
If multi day product, number of days is defined
Status | ||||
---|---|---|---|---|
|
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 firstRenewal-specific product headers must be set up in RTP|One.
Note |
---|
IMPORTANT: Renewal product headers must be distinct from standard non-renewal product headers. So if offering a season pass as a renewal and regular pass product, then create both an ‘Adult Season Pass’ product header for non-renewers and a ‘Renewal Adult Season Pass’ product header. |
Linked Product Component Codes must be set up in RTP|One, linking the previous year’s access component to the current or upcoming year’s linked Product Headers.
Info |
---|
NOTE: To adjust shop’s display order for renewal products: Display order is determined by the display order of product headers associated to the product component in product component link setup in RTP. |
...
Commerce Tasks
Product Shells for Renewal products should be created according to the configuration guide.
Info |
---|
NOTE: Renewal products in Aspenware cannot have an attribute combination table defined and can only have a single SKU for the Aspenware product. Setup separate Aspenware products for Renewal Adult Season Pass, Renewal Teen Season Pass, and so on. |
Settings, Language Strings and/or HTML Widgets for this Feature
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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
Step 1 Header
Step 2 Header
1. Step 1 Header
First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes
Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.
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 | ||
---|---|---|
| ||
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. |
Info |
---|
Note: When possible use notes, warnings, and hints within info panel macros. See https://aspenware.atlassian.net/wiki/pages/resumedraft.action?draftId=781156460 for more details on these. |
2. Step 2 Header
First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes
Sub-bullet for step 1
Sub-bullet for step a
...
DELETE CONTENT AFTER THIS LINE
go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.
To add the feature terms to the Glossary, navigate to the glossary and add a header for your feature using an H2. Select the + and then select …view more. Search for Excerpt Include and in the Page Containing the Excerpt search for “Configuration: [FEATURE]” select to hide panel, preview and add.
How-to Guide of this page can be found here: /wiki/spaces/DB/pages/1040089511
...
Confirm that the following product classification(s) are created.
The ‘Is Renewal Product’ Product Classification must be added as a classification if not already set up as a product classification.
To set the ‘Is Renewal Product’ Product Classification up as a new classification go to Aspenware Commerce>Product Classifications and select Add Classification and define the following fields as follows
Name: Is Renewal Product
Description: Assign this classification to renewal products.
Select the checkbox for Is Renewal
Click Add.
The ‘Renewal Lock’ Product Classification must be added as a classification if not already set up as a product classification.
To set the ‘Is Renewal Lock’ Product Classification up as a new classification go to Aspenware Commerce>Product Classifications and select Add Classification and define the following fields as follows
Name: Renewal Lock
Description: Assign this classification to renewal products.
Select the checkbox for Renewal Lock
Click Add.
Language Strings
Go to Configuration > Languages > English > String Resources, whereyou can set specific language strings that apply to the renewal page. Use the following language strings to edit what customers see in the following scenarios.
If a customer does not have any eligible products, they will see configurable messaging on the renewals or linked product page.
If they are not logged in, they will not see any products and will be shown configurable messaging on the page.
Resource name | Value |
products.renewal.description | Some of your group members are eligible for product renewal |
products.renewal.norenewalproducts | You have no products available to renew. |
products.renewal.norenewalproducts.title | No Renewal Products |
products.renewal.noteligible | It appears that {0} is not eligible for renewal products. |
products.renewal.title | Renewal Products |
HTML Widgets
An HTML widget can be enabled that displays below the category bar and shows configurable messaging that links to the renewal or linked products page for logged in customers and to the login page for users who are not signed in. From Nop Templates > Plugins > HTML Widgets > Manage HTML Widgets, select to edit, or create a new widget for, ‘Renewal Homepage Banner’ widget. From Tools > source code, you can paste in or edit the HTML. The HTML that is configurable is in blue below.
Html widget name | Html content | Widget zone | ||
Renewal Homepage Banner |
| content_before |
Detailed Setup Guide
Step 1 Header
Step 2 Header
1. Create Renewal Products
This task assumes that the prerequisite task of configuring the product shell for the Renewal products has been configured according to this Configuration Guide.
Go to Catalog > Products and choose to Edit the product.
Assign the product to a category that has been set up to be hidden. (Instructions on hiding a category here)
These products are setup as very simple products, so define the SKU and price on the product info tab, unless they are going to be leveraging Aspenware Payment Plan functionality.
Info |
---|
NOTE: IF a product is a renewal product and is going to leverage Aspenware Payment Plan functionality, the following setup is recommended because these products cannot have the product defined on the product info tab and must have the SKU and price defined in the attribute combination table.
|
Next from the Product attributes section, renewal products cannot have a core attribute that has more than one option, but can have add on attributes (see below).
Add the AssignedTo attribute to this product
On the assigned to attribute, add { "lock": true } [Assigned To]. This will lock down the assigned customer so that guests cannot change these options. Ensure that your control type is “Textbox”
In all other attributes, re-enter the name of the attribute. Text needs to be included in the text prompt fields for all attributes, though this will not show for customers.
You can set up add-on products on Renewal products, but they must be control type checkbox and can only use non attributed add on products ( See page 16)
Next from the Specification attributes tab, add the IsRenewal specification attribute to the product. Check Show on product page before adding. This specification attribute ensures that people cannot add these products to their cart if they access these products from a page other than the gated renewal page.
Next, from the Aspenware Commerce Plugins>Product Classifications>Add Assignment page in Admin, select the hidden Category and the renewal product requiring assignment from the category and product dropdowns.
In the Classification table, click the Assign checkbox for Renewal product and Renewal lock classifications
Products flagged with these two classifications will only be available on the (store URL)/renewal or (store URL)/linkedproducts pages if the logged-in customer has previously purchased an RTP product that links to this current product via RTP product component links.