These updates are being added to sandbox alongside the sandbox features and bug fixes from Versions 1.2242 and 1.2244.
Production Sandbox Features
Catalog
- Quick Edit Hover Message: When the product table on the Quick Edits page is locked, a hover message is now displayed to make it clearer that you can’t interact with it until you click the Edit Selection button.
Subscriptions
- Clear Updates Button: When editing a subscription’s next continuity order, you can now click Clear Updates at the top to remove all of these one-time order changes. This will take you back to the original subscription details page where you can click Update Next Continuity Order Only again to start a new version.
- Reset Order Date Setting: A new Subscription setting, Order Now Resets Next Order Date, allows you to determine whether or not the subscription’s next order date is recalculated when you click Order Now to immediately create an order from the subscription. If toggled on, the next order date will be reset based on the current date and frequency. If not toggled on, the next order date that already exists will remain unchanged.
Sandbox Bug Fixes
The following list summarizes resolved issues for this sandbox release.
| Service | Resolution |
|---|---|
| Catalog | Saving a product in Admin would remove multi-value text property values from that product, even though it could be successfully saved via API. This was due to the interface not supporting multiple values for a text-box attribute. This has been fixed so that multi-value properties are not wiped by the Admin when saving a product and the attributes can be used as intended. |
| Inventory | Shipments could not be placed in Backorder when submitting orders to an inventory tag with zero inventory available. Instead, the shipment would be placed in Ready and the inventory was decremented from the tag, causing a negative amount. This has been fixed so that shipments will fall to Backorder when there isn’t inventory available for the applicable tag or inventory channel. |
| Orders | When creating an order from the Admin UI, only the first 25 available locations were displayed in the fulfillment options. Pagination on this menu has been added so that you can now click to see more results and select other locations from farther down the list. |
| Returns | The payment.refunded event was not being triggered after performing a refund from the return page of the Admin UI. This has been corrected so that the event is sent after either a refund has been issued or a return initiated. |
| Site Builder | A generic error message was experienced when trying to save changes to facets in the Site Builder, even though the facet would be successfully updated. This was due to a timeout that occurred with a large number of facets, but did not prevent an individual facet from being updated. Enhancements have now been made to facet performance so that this error is no longer displayed. |
Internal Release Notes
These updates are being added to sandbox alongside the sandbox features and bug fixes from Version 1.2242 and Version 1.2244.
Client-Facing Sandbox Features
Catalog
- Quick Edit Hover Message (QE-251): When the product table on the Quick Edits page is locked, a hover message is now displayed to make it clearer that you can’t interact with it until you click the Edit Selection button.
Subscriptions
- Clear Updates Button (COM-6613): When editing a subscription’s next continuity order, you can now click Clear Updates at the top to remove all of these one-time order changes. This will take you back to the original subscription details page where you can click Update Next Continuity Order Only again to start a new version.
- Reset Order Date Setting (COM-6321 and COM-6322): A new Subscription setting, Order Now Resets Next Order Date, allows you to determine whether or not the subscription’s next order date is recalculated when you click Order Now to immediately create an order from the subscription. If toggled on, the next order date will be reset based on the current date and frequency. If not toggled on, the next order date that already exists will remain unchanged.
Internal Sandbox Updates
The following enhancements are internal-only and not exposed to clients.
- COM-6672: When submitting orders, the new Allocation Status API now validates whether an item got reserved or not.
- CHAR-4383: A limit of 1500 results has now been added to the
pageSizevalue of the Query Inventory API, improving potential inventory performance and making the API more secure when called from the storefront. - CHAR-4355: A new checkbox has been added to the tenant configurations of the Coex Inventory UI, allowing the
risEnabledfield to be enabled or disabled. - TECH-571: Mozu.Catalog has been upgraded to .NET6 and regression testing has been performed.
- Some improvements have been made to the Subscriptions feature:
- COM-6632: An internal API is now available to copy all one-time product and one-tie shipping information into a subscription draft and remove the data from one-time collections. This is to support the new version of one-time changes that are handled via subscription drafts instead.
- COM-6535: Continuity order jobs now account for the subscription draft in the Next Order Only Update page, and create the order from that draft mode while using the Next Order Date and Frequency values from the original subscription.
- Some improvements have been made to the Search feature:
- SU-3099: Search indexing has been improved by replacing the old caching strategy that didn’t work as well in a distributed environment and resulted in incorrectly indexed Solr documents. Now, a standard Redis pattern is used for the Solr schema cache in Indexer/Resolver and the schema manager invalidates the cache when a schema is published before triggering a re-index.
- SU-2969: Code clean-up has been done to remove sort definition references from the Product Runtime service, as the functionality for sort definitions was removed from the search path.
- SU-2808: Errors would be experienced from the schema manager endpoints during Solr configuration deployments and schema migrations, as well as reapplying a migration with the same version. These processed are now handled better so that errors are not returned in migrations and deployments.
- Some work for Order Routing Extensibility (CAT-1721) and Geography-Based User Access (COM-6439) has also been done, but will not be included in release notes until the features are complete. See Jira for the full list of updates.
Sandbox Bug Fixes
The following list summarizes resolved issues for this sandbox release.
| Service | JIRA Ticket | Resolution |
|---|---|---|
| Catalog | CAT-1867 | Saving a product in Admin would remove multi-value text property values from that product, even though it could be successfully saved via API. This was due to the interface not supporting multiple values for a text-box attribute. This has been fixed so that multi-value properties are not wiped by the Admin when saving a product and the attributes can be used as intended. |
| Inventory | COM-6684 (reported by Ssense) | Shipments could not be placed in Backorder when submitting orders to an inventory tag with zero inventory available. Instead, the shipment would be placed in Ready and the inventory was decremented from the tag, causing a negative amount. This has been fixed so that shipments will fall to Backorder when there isn’t inventory available for the applicable tag or inventory channel. |
| Orders | COM-5384 (reported by Bi Mart) | When creating an order from the Admin UI, only the first 25 available locations were displayed in the fulfillment options. Pagination on this menu has been added so that you can now click to see more results and select other locations from farther down the list. |
| Returns | COM-6620 | The payment.refunded event was not being triggered after performing a refund from the return page of the Admin UI. This has been corrected so that the event is sent after either a refund has been issued or a return initiated. |
| Site Builder | CAT-1954 (reported by Client Hardware) | A generic error message was experienced when trying to save changes to facets in the Site Builder, even though the facet would be successfully updated. This was due to a timeout that occurred with a large number of facets, but did not prevent an individual facet from being updated. Enhancements have now been made to facet performance so that this error is no longer displayed. |