- Revision History
- Overview
- Major New Features
- Additional New Features and Other Changes
April Maintenance Pack for 19A
| Date | Feature | Notes |
|---|---|---|
| 03 MAY 2019 | Add Card to Profile | Updated document. Delivered feature in April Maintenance Pack for 19A. |
| 24 APR 2019 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
The April Maintenance Pack for 19A of Oracle Commerce Cloud includes substantive improvements and changes to the product.
What follows is a brief summary. For more details about each feature and improvement, please review the April Maintenance Pack for 19A What’s New document and the official Oracle Commerce Cloud documentation in the Oracle Cloud Help Center.
The major new features released in Oracle Commerce Cloud April Maintenance Pack for 19A include:
For merchants who make high-frequency price changes, OCC now allows for editing prices directly in the storefront, bypassing the publishing process.
OCC Admin users can now filter the change list and publish items without explicitly selecting checkboxes (selecting items one by one or page by page).
Merchants now have the ability to build audiences of registered or anonymous shoppers based on their location as reported by the CDN. Audiences can be built based on Place (country, region, city), Latitude and Longitude, and Time Zone, allowing merchants to present personalized content, products, and promotions to shoppers in different areas of the country, for example.
Additional New Features and Other Changes
There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud April Maintenance Pack for 19A. By functional area, these include:
Browser Support, Language, and Currency Support
Languages: No new languages are supported.
Forty languages are currently supported: Arabic (ar) (Storefront only), Bulgarian (bg), Catalan - ca (Storefront only), Chinese—Simplified (zh_CN), Chinese—Traditional (zh_TW), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en), English-GB (en-GB), Estonian (et), Finnish (fi), French (fr), French Canadian (fr_CA), German (de), Greek (el), Hungarian (hu), Indonesian - id (Storefront only), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Malay - ms (Storefront only), Norwegian (no), Polish (pl), Portuguese—Brazil (pt_BR), Portuguese—Portugal (pt_PT), Romanian (ro), Russian (ru), Serbian - Cyrillic (sr), Serbian – Latin (sr_Latn),,Slovenian (sl), Spanish (es), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk), and Vietnamese - vi (Storefront only).
Currencies: No new currencies are supported.
Sixty-one currencies are currently supported: AED (UAE Dirham), ARS (Argentine Peso), AUD (Australian Dollar), BGN (Bulgarian Lev), BOB (Boliviano), BRL (Brazilian Real), CAD (Canadian Dollar), CHF (Swiss Franc), CLP (Chilean Peso), CNY (Chinese Yuan Renminbi), COP (Colombian Peso), CRC (Costa Rican Colon), CZK (Czech Koruna), DKK (Danish Krone), DOP (Dominican Peso), DZD (Algerian Dinar), EGP (Egyptian Pound), EUR (Euro), GBP (British Pound Sterling), GTQ (Guatemalan Quetzal), HKD (Hong Kong Dollar), HNL (Lempira), HRK (Croatian Kuna), HUF (Hungarian Forint), IDR (Indonesian Rupiah), INR (Indian Rupee), JPY (Japanese Yen), KES (Kenyan Shilling), KRW (South Korean Won), KZT (Tenge), LBP (Lebanese Pound), MAD (Moroccan Dirham), MXN (Mexico Peso), MYR (Malaysian Ringgit), NGN (Naira), NIO (Cordoba Oro), NOK (Norwegian Krone), NZD (New Zealand Dollar), PAB (Panamanian Balboa), PEN (Peruvian Nuevo Sol), PHP (Philippine Peso), PKR (Pakistani Rupee), PLN (Polish Zloty), PYG (Paraguayan Guarani), QAR (Qatari Riyal), RON (Romanian Leu), RSD (Serbian Dinar), RUB (Russian Ruble), SAR (Saudi Riyal), SEK (Swedish Krona), SGD (Singapore Dollar), THB (Thai Baht), TJS (Somoni), TRY (Turkish Lira), TWD (New Taiwan Dollar), UAH (Ukrainian Hryvnia), USD (US Dollar), UYU (Uruguayan Peso), VND (Vietnamese Dong), XAF (CFA Franc BEAC), ZAR (South African Rand).
Browser support is up-to-date.
Customize Emails for Saved Carts
For stores that support saved cart functionality, it is now possible to add the cart name property to email templates to display the name of a saved cart to emails, such as the abandone cart email, to remind customers about items in their saved cart.
Changing the Status of Contact Registration Requests
In the Agent Console, agents acting as delegated administrators can now change the status of a contact request (Accept, Reject, More Info Needed, Review, New) improving workflow efficiencies.
Customizing Countries and Regions in Addresses
New Admin API endpoints at /ccadmin/v1/countries now let merchants add, delete, and update countries and regions available to their store, making it possible to manage a list of countries and regions that have assigned abbreviations for region and display names.
NOTE: Each country and region added must match a valid ISO 3166 code.
Manage Failed Event Webhook Messages
Merchant administrators can now view and resend failed messages using the Admin UI. (Previously, this capability was available via API only.)
Retry Functional Webhook Failures
Allows for the ability to retry functional web hook failures where a failure is defined as any response other than 2xx (e.g. 200 OK), as well as the ability to configure the number of retries for each web hook or disable retry altogether. This is useful in instances where there are intermittent connection failures and a retry is necessary.
Shoppers can now add a saved credit card to their profile without having to place an order. Once saved, this card can be used as the payment method for future orders.
In Design Studio, customers that are using specific layouts or targeting content to specific Audiences can now preview the shopper experience for a specific audience or combination of audiences without having to test on a test site and set up Shopper profiles that correlate to a specific audience rule.
It is now possible to preview a rule that has a read-only, complex "destination,” allowing merchants to preview the effects of rules created via API for “destinations” other than a product collection or search terms.
NOTE: If you preview a rule with multiple “OR” clauses, you are taken to the destination described in the first clause.
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 15 FEB 2019 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
The 19A update of Oracle Commerce Cloud includes substantive improvements and changes to the product.
What follows is a brief summary. For more details about each feature and improvement, please review the What’s New 19A document and the official Oracle Commerce Cloud documentation in the Oracle Cloud Help Center.
The major new features released in Oracle Commerce Cloud 19A include:
We now support Buy Online, Pick-Up in Store (BOPIS) via API and out-of-the-box Storefront widgets. Allows a shopper to order online and choose a store location to pick up the order from. Payment can be done online or in-store. Includes an "online-only" flag for products and SKUs to differentiate items that can be picked up in-store from those that cannot. Also includes API support to associate sites with lists of store locations, as well as distinguish store locations that are inventory locations from ones that are pickup locations.
This feature provides a mechanism to capture BOPIS-specific data, including pickup location, inventory location, contact details of the person picking up the order, available pickup dates and time, and shopper preferred pickup dates and times. OCC webhooks have been updated to support all BOPIS data. New widgets and widget versions have been created to accommodate BOPIS as well, including new versions of the Product Details widget, Shopping Cart widget, Checkout Order Summary widget, Payments widget, Order Confirmation and Order Details widgets, as well as a brand new Shipping Options widget, new BOPIS-related emails, and staged checkout layout specially designed for this feature.
We now support the ability for registered shoppers to save cards and pay for orders (including scheduled orders) using their saved cards. Shoppers can indicate that they wish to save a credit card during checkout and that card will be saved following a successful authorization. At that time, a reusable card token will be returned and saved in Oracle Commerce Cloud. In addition to being able to save cards to pay for future orders, registered shoppers can also set a default card, add or change the nickname for a saved card, and delete a card.
NOTE: This feature is available via API for card payments processed using the Generic Payment Framework in Oracle Commerce Cloud and is not available for out-of-the-box payment gareways.
This is a new enhancement to Dynamic Curation. Merchandisers can now manually curate product listings to promote or "boost" specific products to the top of search results and/or "bury" products at the bottom. This rule can be applied to specific search terms or to a search-driven collection page. The results can be previewed in the Oracle Commerce Cloud Admin to verify the results before putting into production.
Allows merchandisers to select and order facets that appear in Guided Navigation, so that facets can be displayed in an order that reflects common shopping behaviors. Facet ordering can be done based on what will be most useful for shoppers and allows merchandisers to control the simplicity and granularity of the navigation menu for different collections. This rule can be applied to specific terms or to a collection page. Results can be previewed in the OCC Admin before publishing.
Content and Experience Cloud: New "Channel" to Site Mapping
Customers using Oracle Commerce Cloud (OCC) and Oracle Content and Experience Cloud (CEC) can now map different publishing channels from Oracle CEC to sites in OCC allowing the ability to target unique content for each site.
Content and Experience Cloud: New Content Listing Widget
Supports creation of individual listings for each "type" of content in Oracle Content and Experience Cloud (CEC), allowing merchants to create a blog site or index a group of supporting or guidance content and easily manage that noncatalog content through Oracle CEC and present it in the Oracle Commerce Cloud site and shopping experience.
Content and Experience Cloud: New Content Item Layout
Similar to the concept of a product details layout, but for content, this feature allows a page for a content item in a configured channel to be created when there is an integration in place between Oracle Commerce Cloud and Oracle Content and Experience Cloud. Each content item is added to the sitemap and linked where a merchant has set up content lists for that content type.
Content and Experience Cloud: API for CMS Integrations
Primarily built to connect Oracle Content and Experience Cloud to Oracle Commerce Cloud. New Content Map Methods and Channel Map Methods are endpoints for operations that are now available. These APIs can be used to create a site with multiple types of content and add a page for each content item to a page map.
Additional New Features and Other Changes
There are also a number of additional new features, changes, and improvements included in Oracle Commerce Cloud 19A. By functional area, these include:
Browser Support, Language, and Currency Support
Browser support is up-to-date.
Languages: No new languages are supported.
Forty languages are currently supported: Arabic (ar) (Storefront only), Bulgarian (bg), Catalan - ca (Storefront only), Chinese—Simplified (zh_CN), Chinese—Traditional (zh_TW), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en), English-GB (en-GB), Estonian (et), Finnish (fi), French (fr), French Canadian (fr_CA), German (de), Greek (el), Hungarian (hu), Indonesian - id (Storefront only), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Malay - ms (Storefront only), Norwegian (no), Polish (pl), Portuguese—Brazil (pt_BR), Portuguese—Portugal (pt_PT), Romanian (ro), Russian (ru), Serbian - Cyrillic (sr), Serbian – Latin (sr_Latn),,Slovenian (sl), Spanish (es), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk), and Vietnamese - vi (Storefront only).
Currencies: No new currencies are supported.
Sixty-one currencies are currently supported: AED (UAE Dirham), ARS (Argentine Peso), AUD (Australian Dollar), BGN (Bulgarian Lev), BOB (Boliviano), BRL (Brazilian Real), CAD (Canadian Dollar), CHF (Swiss Franc), CLP (Chilean Peso), CNY (Chinese Yuan Renminbi), COP (Colombian Peso), CRC (Costa Rican Colon), CZK (Czech Koruna), DKK (Danish Krone), DOP (Dominican Peso), DZD (Algerian Dinar), EGP (Egyptian Pound), EUR (Euro), GBP (British Pound Sterling), GTQ (Guatemalan Quetzal), HKD (Hong Kong Dollar), HNL (Lempira), HRK (Croatian Kuna), HUF (Hungarian Forint), IDR (Indonesian Rupiah), INR (Indian Rupee), JPY (Japanese Yen), KES (Kenyan Shilling), KRW (South Korean Won), KZT (Tenge), LBP (Lebanese Pound), MAD (Moroccan Dirham), MXN (Mexico Peso), MYR (Malaysian Ringgit), NGN (Naira), NIO (Cordoba Oro), NOK (Norwegian Krone), NZD (New Zealand Dollar), PAB (Panamanian Balboa), PEN (Peruvian Nuevo Sol), PHP (Philippine Peso), PKR (Pakistani Rupee), PLN (Polish Zloty), PYG (Paraguayan Guarani), QAR (Qatari Riyal), RON (Romanian Leu), RSD (Serbian Dinar), RUB (Russian Ruble), SAR (Saudi Riyal), SEK (Swedish Krona), SGD (Singapore Dollar), THB (Thai Baht), TJS (Somoni), TRY (Turkish Lira), TWD (New Taiwan Dollar), UAH (Ukrainian Hryvnia), USD (US Dollar), UYU (Uruguayan Peso), VND (Vietnamese Dong), XAF (CFA Franc BEAC), ZAR (South African Rand).
The Agent Console in Oracle Commerce Cloud can now be customized and extended by a merchant using the existing Design Studio framework (layouts and widgets), allowing customization of the user interface, so merchants can build their own user experience and screens for agents. Includes drag and drop capability to buid custom agent application. Merchants can also now integrate with third party systems to provide a fuller customer experience.
B2C users can now be converted to B2B users if a merchant desires this--typically seen when an orgnaization becomes a B2B account in a merchant's store and users should be able to act as buyers on the account. This is now achievable via API.
Publishing of Individual Design Assets
Users can now select only the design assets they want to publish, as well as filter design assets by author, status, area, and publishing event name or find individual design items via serch query. Design assets, such as widgets and layouts, appear as individual items in the publishing change list. Dependencies are automatically determined and Oracle Commerce Cloud ensures appropriate items are published together.
DCU - Stack and Element Support
The Design Code Utility (DCU) tool now fully supports stacks, as well as global and widget-level elements. It now provides support for creation and transfer of all types of Design components used in Oracle Commerce Cloud.
Developers using the Design Code Utility (DCU) can now speed up the loading of the storefront by limiting the file types that are intercepted by ccproxy. Includes ability to selectively enable/disable which types of design assets should be substituted in ccproxy as part of the Design preview.
HTML Snapshots: Mobile Support
Added support for mobile snapshot when using the adaptive design approach. There is a new endpoint that merchants can configure to determine which user agents will receive the mobile snapshot. Icludes known Google mobile crawlers out of the box.
We've added a framework for presenting type-ahead results using keywords instead of presenting matching products in a list. This can be integrated with a search analytics solution to populate type-ahead suggestions using most popular searches. Can also be extended to include additional metadata, for example, presenting recommended products for each suggestion. NOTE: This is a headless feature, so front-end code needs to be created separately.
Merchants can now build audience rules using UTM query parameters which are commonly used to pass context from referring sites, pay per performance or social advertisements, and other campaigns. So for example, it is now possible to present appropriate content, promotions,, products, and/or experiments to shoppers based on an ad campaign or referrer.
This feature allows merchants to specify that a recommendation set should always show products from a specified collection(s), in the case where there is no product context (e.g. marketing landing page). Also allows merchants to specify the collection of products that should be shown in a content variation slot associated with a particular audience.
Custom Goals for Widget Experiments
Allows merchants to track Pageview custom goals for widget-based experiments. These were previously limited to tracking of out-of-the-box commerce metrics only.
New Goal Type: Commerce Events
A new custom goal type called "Commerce Events" is now available for all types of experiments. Allows merchants to track events as custom goals. These include out of the box commerce events (a refined list of approximately 50 pubsub events), as well as custom events (any event defined by the merchant). These events are tracked in the same way as commerce metrics and removes limitations on what can be tracked as a goal for an experiment.