Announcement: Shipment Workflow Cleanup
The Kibo Business Automation Service hosts Fulfillment Workflows that drive behavior of Fulfiller UI actions and Shipment APIs. This service collects large amounts of data, which is used during fulfillment and then becomes unnecessary once shipments are no longer being acted upon. In order to ensure proper platform performance and minimize maintenance overhead, this data will now be removed after 6 months from the last time it was accessed. This means that if a shipment has not been progressed or viewed for 6 months, then its associated workflow diagram will not be viewable via the Kibo Fulfiller UI and it will no longer have any fulfillment steps available to execute. Shipment data itself is stored in a separate repository and will be untouched.
Any shipments requiring fulfillment steps beyond this threshold, such as a Ready shipment that hasn't been fulfilled yet or a shipment that is still in Backorder, will need to be resolved by reassigning the shipment to either the same location or a new one.
Production Tenant Features
Commerce
- New Payment Events: New event notifications are now triggered for successful Payment.Authorized, Payment.Captured, Payment.Voided, and Payment.Credited events.
- Order Queue APIs: New Order API endpoints (
.../api/commerce/orders/QueuedOrders/and.../api/commerce/orders/QueuedHistoricalOrders) have been created to provide visibility into the order queue, allowing both you and Kibo Support to better investigate any failures while processing orders. These GET calls will return order information with the processing status and any error information if applicable. More detailed documentation for these endpoints will be available and linked here soon.
Search
- Filter By Threshold: When configuring the Vector Search settings of Site Search, a new toggle for "Filter by Threshold" allows you to determine whether or not vector results will be constrained to only products that meet the specified Distance Threshold value.
Production Bug Fixes
| Service | Resolution |
|---|---|
| Catalog | ProductPropertyLocale fields were not updating after importing new values with the Import/Export V3 tool, though they could be successfully updated in the UI. This has been fixed so that you can now update product property locales in bulk through the Import/Export tool. |
| Commerce | In a particular Cybersource integration, an order was rejected and then placed into Pending Review when it was expected to be cancelled. This was due to Kibo's API call to Cybersource timing out, which has now been corrected so that the process will succeed and cancel the order as intended. |
| Fulfillment | When proceeding from the Validate Items in Stock to Print Packing Slip step in the Fulfiller UI, a particular implementation experienced a validation error. This error stated that a unique serial number was missing, though that was not supposed to be a required field. This has been fixed so that STH shipments can still progress without that field. |
Internal Production Details
Find more information about the client-facing updates at these Jira tickets:
The following enhancements are internal-only and not exposed to clients:
- FFMT-3228: Unnecessary indexes have been dropped from Mongo, as many were large and rarely used.
- COM-7992: Though PayPal is not supported for installments out-of-the-box, work has been done to ensure that we can support clients' custom applications for PayPal integration. This has not been included in the public client-facing notes because it is back-end work currently only used by Proactiv's application.
The following bug fixes are internal-only and not exposed to clients:
- CHAR-5332: Sonarlint was not properly measuring multi-module code coverage, reporting zero coverage for code that was actually covered. This has been fixed.
Find more information about the client-facing bug fixes at these Jira tickets:
Production Sandbox Features
Commerce
- Email Length Restriction: Validation has been added to ensure that email addresses on customers and orders do not exceed a maximum limit of 254 characters.
Inventory
- Inventory Tag Restrictions: A default maximum limit has now been placed on how many inventory tags and individual values can be allowed. This limit is 3 tags and 6 tag values (across all tags) per tenant.
Sandbox Bug Fixes
| Service | Resolution |
|---|---|
| Commerce | When orders were placed with valid addresses that didn't include zip codes, such as for UAE locations, shipping methods would not be available. This has been corrected so that these addresses are still accepted and allow shipping methods to be selected for those orders. |
| Fulfillment | Customer Care shipments created from partial quantities of items were missing the fulfillment location code of the original shipment, causing undefined errors during reassignment. This has been fixed so that when some quantity is not available and gets sent to Customer Care, they can be successfully reassigned. |
| Fulfillment | Attempting to generate shipping manifests resulted in an error if any ineligible (such as voided) shipments were included in the manifest. This has been corrected so that manifests are no longer blocked from being generated in this case, allowing valid shipments to be fulfilled. |
| Fulfillment | For a certain implementation, the Create Manifest would appear to spin the loading icon endlessly despite actually creating the manifest in the backend (which was then accessible via the Reprint button). This has been fixed so that the icon stops spinning in the Fulfiller UI when the action is complete. |
| Fulfillment | UPS tracking numbers in the Admin and Fulfiller UIs did not match the actual tracking on shipping labels. This occurred when the fulfiller user mistakenly clicked the Print Shipping Label button more than once. The interface has now been updated to ensure that duplicate clicks will not create additional tracking numbers. |
Internal Sandbox Details
Find more information about the client-facing updates at these Jira tickets:
The following enhancements are internal-only and not exposed to clients:
- CHAR-5352: A deprecated Java version parameter has been removed from the Jenkins file in the Jobs service.
- CHAR-5085: A SFTP/S3 remove server handler has been implemented to improve processes.
- CHAR-5080: A server checker worker has been added to check SFTP endpoints for new files, obtain locks, and emit events for file processing.
The following bug fixes are internal-only and not exposed to clients:
- CAT-4475: On startup, thread exhaustion caused issues connecting to Rabbit. This has been fixed so that changes to Categories, Products, Search Redirects, and Merchandizing Rules entities update the index appropriately.
- CAT-4222: After deploying Mozu.Events to production, various automapper errors were experienced. These have now been fixed.
Find more information about the client-facing bug fixes at these Jira tickets:
- Can't Place Orders Without Zip Code: COM-8406 (reported by Al Futtaim Group)
- Customer Care Errors: FFMT-4222 (reported by Conn's)
- Shipping Manifests Error: FFMT-4202 (reported by Laura Canada)
- Shipping Manifests Spinning: FFMT-4179 (reported by London Drugs)
- Mismatched Tracking Numbers: FFMT-3999 (reported by Tourneau)