DATE:
AUTHOR:
The Shift4 Updates team
APPETIZE [PRE SEPT 2023]

Pre-Release Notes: Connect 12.2 Hot Fix 1

DATE:
AUTHOR: The Shift4 Updates team

Need more information? Email enterprisesupport@spoton.com or call (877) 559-4225. The Support team is available 24/7/365.


Target Release Date: 22 March 2023
Release Version: CON_12.2_HF1
Content: Connect Bug Fixes


Feature updates:

  • Inventory - Standsheets - Optimized queries that move standsheets to count out status. This improvement will improve latency and reduce the risk of overload on the database.

  • Inventory - True Up - Optimized True Up queries that were causing excess latency. This optimization will make item lookup in the True Up flows more performant

Bug fixes:

  • 'Pending' planned transfers were not being created for each selected vendor, and transfers that were created had items missing. The root cause was an invalid character being inserted into the item transfer counts that caused the transfer to fail. This does not consistently happen on the same items, so a short-term fix was implemented to replace the invalid character in the inventory transfer amount with a zero (0).

    Where does this bug appear in the transfers flow?

    • Pre-condition: Create an event. (This will put the event in ‘Created’ Status)

    • Create a pending transfer in the plan a transfer flow. 

      • Defect may occur here with some items show zero (0) transfer amounts

    What impacts will this short-term fix have operationally? 

    1. Some items in the ‘pending’ transfers will have a ‘0’ value

    2. For the items with a ‘0’ value, a new pending planned transfer must be created and targeted to the same event

    3. Leave the event in ‘created’ status

    4. Once the new transfers are in a ‘pending’ state, review and validate there are no zero (0) values for any items in those transfers 

    5. For a detailed step-by-step guide on the process, see the steps in the appendix.

    6. Only move the event to open status once all transfers for all items are correctly created in ‘Pending’ status.

    A long-term solution will be implemented later, preventing the invalid character from being created.

Powered by LaunchNotes