Production Tenant Features
There are no features targeted for your production tenants.
Production Sandbox Features
Curbside Functionality
- Notification Updates: Previously, the Customer In Transit and Customer At Curbside events only triggered SMS notifications to the fulfillment location to inform them of the customer’s status. This process has been extended to include email messaging, so that the fulfillment locations will now also receive email notifications for these updates. Note that was functionality mentioned in the previous version release, but now the associated email templates have been added to the sandbox.
eCommerce and Order Management Functionality
- Support Legacy Fraud Data: The transformation (or translation) layer that converts legacy OMS API requests to the new KCCP APIs now includes support for the fraud section of the Create Order API, allowing CyberSource fraud information to be properly ingested for legacy clients and update order fraud statuses.
- Order Queue Enhancements: Enhancements have been made to improve the performance of the order queue when ingesting an imported order management order. The caching on site setting API calls has been improved to better support the order import.
- Mobile Fulfiller Navigation: On mobile applications and browsers, the user is immediately directed to the FFUI dashboard upon login if they are only a user of one possible tenant. In the browser, a fulfiller user is not able to navigate to the Admin UI. This does not apply for administrators with access to multiple tenants, as they are able to select their tenant and use the Admin UI.
- Sync Site and Location Group Settings: A button to “Sync All Sites” is now displayed in the site settings and location group configuration settings of the Admin UI, based on whether that ability has been enabled for the tenant. When enabled, clicking this button will sync the chosen settings across all sites on the tenant. This makes it easier to manage and update different site level settings when there are a large number of sites on one tenant, as clicking the button once will update the data on all sites.
- Variant Properties: Variant-specific properties can now be defined for configurable products, in which attributes have different values depending on which product variant is currently selected. For example, solar panels from the same line come in different wattages that each have their own dimensions and efficiency rating. The wattage options are the variants of the panel product, while the dimensions and ratings are the variant-specific properties. As the customer selects different wattages, the associated property values will be updated to match their variant selection. Any existing attributes that are the “property” type can be enabled as available variant properties in the Product Types configurations of the Order Admin UI. They can then be managed at the product variation level when editing variants in the Products view.
Bug Fixes
The following list summarizes resolved issues for this release.
| Status | Resolution |
|---|---|
| Targeted for Production Sandboxes | If the extraEntries field, such as for identifying additional attributes, was included in the Bulk Add Entries API request for pricelists then the call would fail with an unexpected error response. This has been fixed so that extra entries can be successfully provided for price lists via this bulk API. |
| Targeted for Production Sandboxes | Order Routing data lists were being created with location ID values rather than the intended location codes, preventing these lists from being used properly. This has been updated so that data lists reference the proper field for both creation and retrieval of data list location information. |
| Targeted for Production Sandboxes | Order Routing could not properly interpret the custom item data that was passed by transformed legacy OMS APIs, preventing this data from being used in routing filters. This has been corrected so that custom item data is communicated more clearly to Order Routing. This transformation (or translation) layer is the process that allows legacy OMS API requests to work with the newer KCCP APIs, so this update is an automatic process that does not require changing calls being made to Order Routing on the user’s side. |
| Targeted for Production Sandboxes | The “Finish Fulfilling Shipment” button was not always being displayed for particular locations in the FFUI, though the button would be shown if All Stores was chosen from the store selection dropdown. The logic that determines when to display this button has been updated, so that the UI looks at the current user’s store associations instead of the store selection button. Thus, the button is now always displayed for available shipments if the user has the appropriate permissions and is associated with that location. |
| Targeted for Production Sandboxes | Shipping manifests were sometimes unable to be generated, though no error was displayed on the page. This was partially due to the Create Manifest button remaining clickable on the page after beginning the process, as clicking the button multiple times caused the creation call to fail. Enhancements are in progress to improve the response time of manifest creation, while the button has been updated to be disabled while the creation is in progress. |
| Targeted for Production Sandboxes | An order remained in an infinite reassignment loop after experiencing an error that caused an item to be stuck in pending status for allocation. This inventory service has been updated to avoid similar loops in the future and otherwise improve the efficiency of the allocation process. |
| Targeted for Production Sandboxes | If a tenant used “TISPU” instead of “ISPU” then custom state codes for the fulfillment process failed to be overridden. This has been corrected so that TISPU (the preferred acronym for pick-up in KCCP) properly supports custom states. |