August 10, 2021 — 1.2130 Service Update

Production Tenant Features

Order Management & eCommerce Functionality

• Removed BOPIS Return Labels: The button to print return shipping labels has been hidden from the BOPIS shipment view of the Order Admin to avoid confusion about this functionality. Return labels could not be printed for returns generated from BOPIS shipments, which was the intended behavior. This is due to the fact that BOPIS items are not expected to be returned via shipping as they would for a STH order, and thus do not have an applicable “Ship to” address.
• Max Packing Slips Location Config: A new configuration option has been added to location group settings, in which the user can set a “max. number of packing slips by group.” This setting is optional but providing a value will override the default value of 10 that is already used by the system. This determines how many packing slip tabs can be displayed in the Fulfiller UI’s Pick & Pack feature.
• Block Assignment in Cancel Shipment API: The blockAssignment flag that blocks future assignment to a shipment’s original assigned location has now been added to the Cancel Shipment API. This allows assignment to be blocked from that location when you cancel one of its shipments.
• Transfer Child Relationships: Similarly to the functionality used for service items, BOPIS and Transfer shipments now use item IDs to denote the relationship between parent and child items. The “parent” item in a BOPIS shipment includes a childItemId parameter pointing to the transfer item. In the Transfer shipment, the “child” item has a parentItemId parameter pointing back to the BOPIS item. This relationship previously existed at the shipment level but has been extended to the line item level to support behavior where an operation performed on a parent item also reflects on the child item being transferred. This is implemented on all transfer instances.
• NativeScript Print URL Updates: Print URLs have now been updated to PDFs in the NativeScript application. This allows documents such as shipping labels, packing slips, and pick sheets to be successfully printed in the proper PDF format.
• Tax Recalculation: When tax integration is not available, the Kibo Composable Commerce Platform will now recalculate tax based on the given tax percentages instead of refreshing the tax. This uses the Arc.js actions documented here. When both item and shipping tax rates are provided at the item level, then the Kibo Composable Commerce Platform will apply those tax rates to the line item upon a change in shipping address, change in line item unit price, or adjustments to item or shipping subtotals.
• Fulfiller Dashboard Defaults: This feature was originally released to sandbox with 1.2124 but is now being pushed to production with updates from 1.2128. Theme customization for the Fulfiller UI now supports defining a default tab for the dashboard to determine which shipment listings are displayed first when the page is opened. In the theme language files, the “SHARED.TENANTSETTINGS.defaultDashboardTab” setting can be set to a particular shipment type in order to set that shipment type’s tab as the default. For instance, setting “defaultDashboardTab“ : “BOPIS” would result in BOPIS shipments being displayed upon opening the dashboard. This allows the Late Shipment tab, which is the out-of-the-box default, to be removed from the UI with the following code: .alert-tab-Late { display:none; }
• Shipment Item Declined Subscription: The existing SHIPMENT_ITEM_DECLINED event has been added to the available event subscriptions in the Dev Center, allowing users to subscribe to these events through the user interface. This event is triggered by actions such as cancel shipment item, shipment reassign, reject shipment, and transfer shipment. When the event is triggered, information about the action will be delivered through the subscription. See the Event Subscription and Shipment Event Notification guides for more details. Note that these docs are intended to be revisited and may be merged together in the future.
• Return to Gift Card from Fulfiller UI: Any return processing for gift card payments via the Fulfiller UI would result in a failure. This was due to the Fulfiller UI's return logic attempting to perform a payment credit, which was not supported for gift card gateways. Now, the return process will allow the fulfiller to select "Process to New Gift Card" while handling a return, which will create a new gift card under the order's customer name and email address which the total amount of the refund will then be applied to. See the Fulfiller return processing documentation for more information.

Translated Order Management Functionality

• Location Mappings: When a tenant using the translated Order Management APIs adds a new location from the Admin UI, the system now automatically maps the location data so that it can immediately be used by the Inventory and Order Routing services. Previously, this did not happen automatically and required an engineer to manually perform the mapping.
• Translated Tax Overrides: Previously in the Create Order API, an error would be returned if values for both itemTaxOverride and itemTaxRateOverride were sent. Now, the itemTaxOverride field will override the itemTaxRateOverride field. Likewise, the same error would be returned if values for both shippingTax and shippingTaxRate were sent. Now, the shippingTax field will override the shippingTaxRate field at both the order and item level. All of these values also accept decimals up to 5 places. For more information about these translated APIs, see the documentation.
• Item Identifiers: Item identifier data is now returned in translated GET calls to the Order, Item, and Shipment APIs to facilitate importing and retrieving orders. The data can be updated when sending a request to the translated Transition Shipment State API to validate items in stock or validate an incoming transfer. This also supports the Fulfiller UI, as it allows fulfiller users from upgraded implementations using translated APIs to set their item identifiers (such as card numbers) in the FFUI and then view that information in their Order Admin UI and transactional logs. For more information about these translated APIs, see the documentation.
  When transitioning states, the user can update item identifiers such as in the below example. In GET responses, the array format is the same but the object is called customFulfillmentFields.

  “fulfillmentFields”: {
      {
          “key”: “Card Number”,
          “value”: “123”,
          “required”: true
      }
  }

Production Sandbox Features

Order Management & eCommerce Functionality

• Flexible Auto Capture on Delivery: Shipments of the Delivery fulfillment type will now reference the existing flexible auto capture setting used for BOPIS orders in order to determine when payment is captured. See the Delivery and Auto Capture documentation for more information.
• Tax Recalculation on Refunds: Similar to the Tax Recalculation update released with Version 1.2128, tax is now recalculated when a return is initiated and the user issues a refund. This calculation is based on the item tax value and ensures that the automatically-generated refund is for the appropriate amount.
• Refunded Gift Card Number: When a refund is performed to a new gateway gift card, the full gift card number is now displayed in the Returns and Payments tabs when viewing an order in the Order Admin UI. This allows CSRs and Admins to reference the new gift card’s number if needed for the customer.
• Order Grid Update: A minor update has been made to right align the amount fields in the Orders grid of the Admin UI.

Order Management & Fulfiller Functionality

• HTML Pick Wave APIs: API support has now been added to retrieve the HTML data of pick lists and pick wave documents. This allows these documents to be printed via API rather than through the Fulfiller interface. These GET endpoints are: /commerce/shipments/{shipmentNumber}/rendition/html and /commerce/pickwaves/{pickWaveNumber}/rendition/html. The API documentation will be updated here with the release of this Kibo Composable Commerce Platform version.
• Order Routing Filters API: A new Order Routing API endpoint (…/group/add-filters) has been added to support adding multiple filters to a location group. The request payload only requires a list of filter codes and the identifier of the group that those filters should be added to, as shown below. Order Routing API documentation will be updated here with the release of this Kibo Composable Commerce Platform version.

  {
      "selectedFilters" : [1,2],
      "groupID" : 1
  }

• Custom BPM Update: A particular implementation’s custom BPM, used to transmit shipments to SAP, now has associated updates in the Fulfiller UI to facilitate that process. These updates add buttons for Done, Skip, and Back to allow fulfillers to navigate between (though not every step has every button, such as Skip not being allowed when receiving a transfer). This does not affect other fulfillment flows, such as the standard STH and BOPIS, that already include UI buttons to continue on to the next step.

B2B Functionality

• B2B Account Hierarchy Update: When viewing the B2B account hierarchy on the storefront, the area where the hierarchy tree displays would be blank if the account was not part of a hierarchy. To reduce user confusion and assist them if they choose to add child accounts, a default root account node will now be shown with the current account name for those cases. See the B2B documentation here for more information about this hierarchy.

Search Functionality

• Typo Tolerance vs. Min Match: Note that this feature was added to sandbox in Version 1.2128 but has now been moved to 1.2130. The Typo Tolerance options in the site search configurations are now hidden when Min Match is in use. These features cannot both be active at the same time, so Typo Tolerance will not be displayed if Min Match is set to a percentage other than 0 percent. It will be available only when Min Match is set to 0 percent. For more information about these features, see the documentation.

Bug Fixes

The following list summarizes resolved issues for this release.