> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kibocommerce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# November 26, 2024 - 1.2446 Service Update

## Announcement: Code Freeze

Kibo has entered its "code freeze" for the peak holiday season, in which no more updates will be pushed to production tenants. Changes will continue to be added to sandbox environments per the below schedule and will be released to production on January 21, 2025:

* [Version 1.2442: October 29](/release-notes/october-29-2024-12442-service-update)
* [Version 1.2444: November 12](/release-notes/november-12-2024-12444-service-update)
* Version 1.2446: November 26
* [Version 1.2448: December 10](/release-notes/december-10-2024-12448-service-update)
* [Version 1.2452: January 7](/release-notes/january-7-2025-2452-service-update)

## Production Sandbox Features

### Catalog

* **Discounts Tooltip**: A tooltip has been added to [discount attribute configurations](/pages/configure-discounts#attribute-conditions "Configure Discounts") to remind the user that disabling and editing attributes could affect whether their discounts apply as intended or not.

### Commerce

* **Hide Substitution-Only Products**: A new [product property attribute](/pages/property-attributes "Property Attributes") called Hide Product (system\~hide-product) has been created for implementations with [substitutions](/pages/substitute-products-overview "Substitute Products") enabled. If set to a value of "SubstituteOnly", the product will not be indexed or returned by the Get Products API. This means that it will not be displayed on the storefront or in search results, and will only appear while selecting a substitute product. You can still retrieve these items with the [Get Product Substitute](/api-reference/storefrontproducts/get-product-substitutions) endpoint.

### Fulfillment

* **Aborted Shipment SLA Status**: If an active SLA definition is deactivated, then all shipments with that SLA will now be updated with an `slaStatus` of "Aborted" as seen in their [Get Shipment API](/api-reference/shipment/get-shipment) response.

### Order Routing

* **Candidates Suggestion Sorting**: The Candidates Suggestion API now supports a sort field to order results based on their routing group. When `"sort": "SUGGESTION_SORT"` is provided in the request, then locations within a group will be sorted based on that group's rule, such as distance or rank. Note that sorting does not happen across groups, meaning that if there are two groups sorted by distance and the shortest distance is in the second group, then that candidate will not be the first result (because the entirety of the first group will be listed before the second group). The API documentation will be updated soon with this new field.

## Sandbox Bug Fixes

| Service   | Resolution                                                                                                                                                                                                                                                                                                                                                              |
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Fulfiller | The URLs for FedEx SmartPost tracking numbers were not working in customer facing emails. This has been fixed so that these links work as expected.                                                                                                                                                                                                                     |
| Fulfiller | The Reassign Shipment API transitioned shipments to Customer Care status when the call included an `x-vol-tenant` header but not `x-vol-site`, because the system then passed the Tenant ID as the Site ID and caused an error. This process has been updated so that when `x-vol-site` is missing, the correct Site ID will be retrieved based on the shipment number. |