Follow the instructions below to configure products using the new Cloud UI Product Detail Page.
...
If the product is configured to show the pricing calendar as the landing page, ensure the Cloud UI Full-Page Pricing Calendar is set in advance.
Configure Product Shell and Product Attributes as usual, but consider the following differences for the Cloud UI PDP.
[Dynamic] and [Conditional] are no longer needed as the Dynamic box is not used for the Cloud UI PDP and conditional logic will be driven off the Conditional Attribute setup described in Section 5 of the Product Attributes Configuration Guide.
Cloud UI offers better coach messaging if an attribute is required but not preselected. Defaults no longer need to be defined unless the product uses the pricing calendar.
Upgrade your Experience is a configurable Language String (see below)
Attribute descriptions are configured differently from what is documented in section 6 of the Product Attributes Configuration Guide. Follow the instructions below for Attribute descriptions.
Meta title text and price from related product’s configuration pulls through on related product cards.
When adding links in product descriptions, for these links to inherit theme customizations,
class="ads-link"must be added to the link HTML. For exampleGo to this <a href="{LINK}" class="ads-link">LINK TEXT GOES HERE</a>has the class, but the following link does not:Go to this <a href="{LINK}">LINK TEXT GOES HERE</a>
Flag products that are not compatible with Cloud UI so that they continue to render in the Legacy UI. See section 1 below for flagging instructions and a complete list of incompatible product types.
Product Inline calendars on the Cloud UI PDP now automatically display the month with the first available date, eliminating the need for guests to cycle through months to find it. This update makes booking more convenient. If you have enacted the recommended work-around to default the calendar to the first available month, this should be removed from products moving to the Cloud UI PDP.
...
For these listed exception products, there is a new product-level setting that enables some products to continue to load for users in the Legacy UI, and for the majority of products to load in the new Cloud UI. Respecting this routing will work whether a PDP is accessed via the category page, related product link, or cross-sell link. To flag a product so that it continues to load in the Legacy UI:
Find the product from Catalog > Products >Edit
Scroll to the Aspenware Commerce section of the edit page
Locate the new product-level setting called Use Legacy Product Page.
Check the box
Click SAVE ALL SETTINGS
| Info |
|---|
NOTE: This setting should ONLY be turned on if a product is incompatible with Cloud UI. |
...
To edit product attribute titles and descriptions:
Go to Catalog > Attributes > Product Attributes
Scroll to the desired attributes and select Edit
Edit the attribute as indicated below
Click Save
Attribute titles and descriptions can also be displayed for add-on product selections, to better explain the add-on, as in the example below.
...
To edit product variant names:
Go to Catalog > Products
Edit the desired product.
Expand the Additional Product Settings section. Within this section, if attribute combinations are defined, each attribute combination will be populated in the table and can be edited.
...
To edit product variant names:
Go to Catalog > Products
Edit the desired product.
Expand the Additional Product Settings section. Within this section, if attribute combinations are defined, each attribute combination will be populated in the table and can be edited.
If you want to configure the max price but not show it to the guest, you can hide savings information on the product or add on product itself within the Aspenware Commerce settings section. To hide savings information from displaying to guests uncheck “Show Max Price” and select Save All Settings. Show Max Price is true by default for all products.
...