February 22, 2022 — 1.2206 Service Update

Production Tenant Features

eCommerce & Order Management Functionality

  • Reserve Inventory for Pending Review Orders: A new site setting called “Allocate Inventory for Orders in Pending Review Status” has been added that when enabled, will automatically create shipments for Pending Review orders and reserve inventory for them. These shipments will be temporarily blocked from fulfillment in the Fulfiller UI until the order is accepted. By default, this setting is disabled and shipments are not created until an order is accepted. If the order or shipments are cancelled, the inventory will be deallocated.
  • Accept Order Error Handling: Some new behavior has been added to better handle failures encountered during the Accept Order step. As creating shipments is a step of the acceptance process, it was possible for shipments to be created and then duplicated if the order failed and had to be re-accepted. To prevent this from happening, if a failure is encountered during acceptance then any shipments that were already created for the order will be canceled. When the Accept Order step/call is made again and the order is successful, new shipments will be remade.
  • Backorder Reauth Setting: The “Payment Void and Reauth” site setting that was added with Version 1.2202 has been fully synced with the behavior logic so that this option is fully supported. To recap, this option supports disabling backorder re-auth for clients who may be using subscription tokens that don’t expire and thus do not need payments re-authed when the backorder is released. This can only be enabled if the Backorder Job setting is enabled first and it will be enabled by default for clients who are using backorder jobs. 

Fulfiller Functionality

  • Split Packing Slips: Fulfillers can now split packing slips for when you want to pack and ship items separately that are part of the same order, such as when items do not fit in the same box due to size, weight, or other factors. The Print Packing Slip step of the Ship to Home and Transfer fulfillment flows allows you to indicate which items should be included in each slip, while the Prepare for Shipment step allows you to print those shipping labels and add different tracking information for each slip.
  • Pick Wave Sorting: In Version 1.2202, the Pick Waves API was updated to allow sorting GET results based on inventory locator name. However, this sort field is now slightly changed to /?sortContents=contents.locatorName  or /?sortContents=-contents.locatorName. Recall that to sort pick waves in the Fulfiller UI, you must customize your FFUI theme and enable the tenant setting pickWaveDisplayFields.locatorName.enableSorting.

Search Functionality

  • Search Settings UI Updates: Several updates have been made to Search Settings.
    • The Schema Editor page title has been changed to “Search Schema.”
    • Campaigns have been renamed to “Merchandizing Rules."
    • The Search Synonyms, Search Settings, and Search Redirects links have been removed from the Marketing tab of the nav menu and replaced with a single “Search” link, so that all search features are accessed via a common menu item.
    • Icons have been updated for the sub-menu items in the navigation menu on the Search page.
    • When on any page, its label in the nav menu is now bolded.
    • Permissions have been updated so that users must have a role with appropriate Read behaviors to see the search, schema, merchandizing rules, synonyms, and term redirects pages.
    • The noun_extraction analyzer was being shown as an option for custom fields as well as in the category and product suggestion options, which was not allowed.
    • A description for the noun_phrase analyzer has been added.
    • Any tenants who had _pf fields with phrase weights >0 to 0 have been migrated and updated so that those phrase weights have been set to 0.
    • Since _pf fields are only allowed to have a phrase weight of 0, the ability to edit this has been disabled in the UI.

Production Sandbox Features

eCommerce Functionality

  • Campaigns: Campaigns allow you to design marketing strategies across your site by coordinating product displays on the storefront along with promotions. Campaigns consist of a set of discounts and page variations that can be enabled during a particular time frame, allowing for seasonal promotions and storefront user experience to be more designed and managed as one event.
  • Quick Edits User Permissions: Permission behaviors have been defined to allow certain users to utilize the Quick Edits feature. Users only need to have a role that includes the following read/update permissions for products and categories: Product Update, Product Read, Publish Product Changes, Product Category Read, and Product Category Update. This will allow them to use the Quick Edit menu in the Catalog > Products page.
  • Discounts & File Manager UI Updates: Some UI adjustments have been made to both the reworked Discounts and File Management pages. Green is now used for highlighting action buttons instead of blue and the button styling across pop-ups is more consistent with the rest of UCP.

Order Management & Fulfiller Functionality

  • Pick Wave Updates: The Fulfiller UI’s pick waves page has been edited to better reflect options that were carried over from the previous version of OMS. Previously, the page displayed the option for a “special” pick wave type that was not supported in UCP. This option has been removed and the remaining options have been renamed to be clearer:
    • Normal = All Item Shipments (Includes Single and Multiple Item Shipments)
    • Single = Single Item Shipments
    • Multiple = Multiple Item Shipments 
  • Additionally, the back-end logic for generating pick waves has been updated so that similar line items will be grouped together across shipments. This behavior will be extended to the Fulfiller UI in the future.  For example, if 5 shipments have 1 quantity of Product 123, the pick sheet will show one parent row for Product 123 with a quantity of 5 and display child rows beneath it for each individual shipment that has a quantity of 1. This makes picking items more efficient and the sheet easier to reference.
  • Unique Shipment Notes: Internal notes can now be added to a specific shipment via the Shipment API, in a similar manner and validation to order notes. These do not persist across child shipments – they are only associated to the shipment they were originally created on, and will not be displayed at the order level either. The ability to view and edit these notes will be added to the Order Admin and Fulfiller UIs in an upcoming release. The existing functionality to add a note to a shipment that is applied to its order remains unchanged – this “Add Note” option is actually an order note and not visible on the shipment.

    The Shipment API now supports new calls for POST .../shipments/{shipmentId}/notes to create a new note on a shipment, and PUT and DELETE calls for .../shipments/{shipmentId}/notes/{noteId}. This data will be saved and returned in a shipmentNotesobject from a GET Shipment call. The request to create/update a note should define the note text, the username, and role of the user creating the note as shown below. The timestamp will be automatically recorded. 
        “noteText”: “Sample Note Text”,
        “role”: “Superadmin”,
        “username”: “Kibo 123”
  • Shipments in Solr Update: In Version 1.2202, shipments were added to Solr indexing to improve shipment query performance. This process has been switched from opt-in to opt-out, meaning that queries will be made through this index by default. If you wish to opt out of this indexing while making GET Shipments API call, you must provide the ?bypassSearchIndex=true query parameter in the endpoint. When set, this will retrieve results directly from the database instead of through Solr.

Translated OMS Functionality

  • Credit Cards in TLogs: All types of transaction logs will now return the actual last four digits of a credit card number, instead of the token, for clients upgraded from the previous version of OMS who use the ccLastFour field added to the Order API in Version 1.2146. Previously, these four digits were only the last four digits of the cardNumber field, which was actually the card token. For eCommerce and eCommerce+OMS implementations, these token digits were the same as the actual last four digits of the card. But for Order Management-only implementations, the token was often different. Thus, the ccLastFour field allows the actual last four digits to be specified during the order import process, and the logs will display this value (if provided) instead of the token. See the translated Order Import API.

Search Functionality

  • Search Settings UI Updates: Additional updates have been made to the Search UI:
    • The Search Redirects page title has been changed to “Search Term Redirects.”
    • The _ta (type ahead) analyzer option is being removed from Site Search and a migration has been performed so that functionality is not broken by clients updating fields/analyzers that were allowed but should not have been. It is still valid for Product and Category Suggest.

Bug Fixes

The following list summarizes resolved issues for this release.

Targeted for Production TenantsAfter entering a return reduction when performing a return in the Fulfiller UI, the reduction was not included in the credits transaction log. The entire return amount was being reported in the returns transaction log instead. This logic has been updated to properly calculate return reductions and display the values as expected in the logs.
Targeted for Production TenantsThe logical operators for Order Routing’s “distance from fulfillment location to order” filter attribute did not appear when editing a filter that had that attribute already selected. This has been fixed so that the logical operator options will be properly displayed.
Targeted for Production TenantsWhen a Customer Care shipment belonging to an upgraded OMS client was moved into the Ready state, an event notification was not triggered due to errors retrieving location data. This has been fixed so that notifications will be successfully created and sent for these cases.
Targeted for Production TenantsA 404 Error was occasionally experienced in the Order Routing UI when the webapp failed to initialize. The error handling logic has been updated to improve how this scenario is handled.
Targeted for Production TenantsDelivery shipments were incorrectly passing the “DIRECTSHIP” order type to Order Routing when creating transfer shipments, instead of “TRANSFER” types. This resulted in incorrect routing suggestions for these transfers, but this has now been corrected so that transfers for delivery shipments are properly handled.
Targeted for Production TenantsOrders that were captured on CyberSource occasionally did not have that payment record displayed in Kibo and their payment stayed in the Authorized state, when flexible auto capture was enabled after validating items in stock. This has been fixed so that the payment records for this case are properly updated.
Targeted for Production TenantsSeveral issues have been fixed in the Search API and the Search Settings UI.
  • The PUT schema API required spelling fields to be included in the request, which was not necessary. These fields are now optional.
  • The UI’s delete on hover color was not consistent across all search types.
  • The alignment and text boxes for slicing, min match, and phrase slop configuration options were not displayed correctly in the UI.
  • The modal warning for navigating away from the settings page without saving has been updated with more consistent design.
  • The search preview information box used the wrong text size.
  • The whitespace cross field factor’s supporting text label was appearing below the input field instead of next to it.
  • A long URL in the search term table would overlap with other columns in the table, instead of being cut off with an ellipsis.
  • The active and inactive buttons for Redirects were not the same size.
  • Tags and various delete modals were not displayed with the proper styling.
  • In the Schema Editor, hovering over catalogs unnecessarily highlighted them as no action can be performed on them in the schema.
  • The noun_extraction option was not being saved to the UI form. 
Targeted for Production SandboxesWhen a single shipment package collection included multiple tracking numbers, all shipments on the order would not be displayed in the Order Admin, though they were in the Fulfiller UI. This has been fixed so that more than one tracking number does not cause errors and the shipments can be viewed in Admin.
Targeted for Production SandboxesThe Partial Pickup Ready email was triggered instead of the Order Pickup Ready email when some items on BOPIS or Curbside shipments were declined and canceled. The intention of these emails was for Partial Pickup to be triggered when some items were being transferred to be picked up later, but in this scenario the canceled items will not be available for pickup later. Thus, the fulfiller behavior has been updated to send Order Pickup Ready notifications in this case.
Targeted for Production SandboxesThe Fulfiller UI’s Prepare for Shipment section displayed all courier options in Kibo’s system even if they were not enabled for that fulfiller. This has been fixed so that only the enabled couriers will be available for selection during shipping.
Targeted for Production SandboxesA fix was previously made for shipping addresses in Version 1.2202, in which the second address line was not displayed in the Fulfiller UI’s customer information. However, additional “undefined” text labels were being displayed after the fix was implemented. These have been removed so that the address is shown properly.
Targeted for Production SandboxesIt was possible for two or more users to fulfill the same shipment at the same time via the Fulfiller UI (or one user modifying the shipment in two tabs), causing an issue where the label and tracking number were generated but then removed. The UI has been updates to handle this scenario and ensure that changes are not overwritten by multiple users and tracking numbers cannot be removed from a fulfilled shipment.  
Targeted for Production SandboxesPay With Amazon was unable to be installed to a particular implementation’s production tenant, as attempting to do so resulted in an undefined error instead. This was due to the tenant having a large number of sites, and the application has now been installed for them by Kibo Engineering.
Targeted for Production SandboxesThe unit of measurement selection in the Order Routing filter settings was not saving – if miles were selected, it would be reset to kilometers after opening the filter again. This has been fixed so that the option can be properly configured.
Targeted for Production SandboxesA particular implementation was experiencing null errors at the production variation level when exporting order data. This has been corrected so that orders can be successfully exported.