July 8, 2020

VPS 3.23.2 and 3.23.3 Release Notes

July 8, 2020

VPS 3.23.2

New Features

None.

Enhancements to Existing Functionality

NGDT-1245 and NGDT-1251- Load Screen:  Add additional error handling to avoid a route from being re-released (CNE – South Windsor)

Occasionally, a user could release a route that had already been released because the route appeared to still have a Built or Committed status due to a delay in updating the workstation VPS load screen display.  Although VPS is designed to perform the various screen refreshes, there were isolated situations where it did not happen.  Because of this possible delay, additional error handling has been added.  A check has been added to the Load State Updater core plug-in to ensure that if there is any mismatch of the load statuses an error will be presented to the user.  This will be displayed with the red circle  on the route with the issue:

If the user attempts to release the route, they will be presented with the following message and will be unable to continue:

Bug Fixes

NGDT-1195 – Hourly Vmail:  The Production Detail Report not including the most current hour (CCBCU)

A customer noticed that the Production Detail report was not including the most current hour.  For example, when the 3PM hourly reports were sent, the last hourly report on the Production Detail report was for the time 1 PM to 2PM, missing the 3 PM information.  The Production Detail report uses data supplied by PLC inserted system production messages. When the hour rolls around, the Vmail Hourly is sent.  The hourly totals are calculated on the system production message “Containers Last Hour”.  Code has been added to wait for this message to be logged before sending the Hourly Vmail.

NGDT-1232 – Build Error:  Live routes build error due to product changes made to staged pallets (Superior)

A build error occurred when VPS was attempting to calculate the build height of a staged pallet.  After researching, it appears a product had its dimensions modified between when the staged pallet was built (on the Staged Route) and when the Live route was built (later in the day’s run). The product dimensions violated the pattern used to build the staged pallet and therefore when the build height was calculated a build error was thrown. The build logic was adjusted to have VPS pull the build height information from the already built staged pallet at the time the Live route is building.

NGDT-1266 – Sideload Aggregate Build Logic:  Implement HSPA building logic (PBV)

A change has been made to the Sideload Aggregate build logic to perform the building of HSPA pallets when using this build type.  Currently, pallets that could be built at the HSPA location are going through the system and building pallet.  The logic has been corrected to allow the building of HSPA pallets.

NGDT-1271 – Sideload Aggregate Build Logic:  Implement Package Type setting Max Layer Per Pallet  (PBV)

An addition has been made to the Sideload Aggregate build logic to look at the Max Layer Per Pallet assigned to a package type when using this build type.  Currently, a pallet builds based on a combination of settings.  This will now include the setting on the Package Type.  This setting allows the user to limit the number of layers for the package type.  For instance, for a heavier product a customer can limit the number of layers.  This will allow lighter and more stable pallets created online.

VPS 3.23.3

New Features

None.

Enhancements to Existing Functionality

NGDT-416 – Build logic problem (CCBCC-Clayton)


The original issue was that a smaller pattern was built at the bottom of the pallet.

With VPS’s latest installers, the pallet builds with the smaller pattern on top whether or not the package type has a default pattern assigned.

Bug Fixes

NGDT-1240 – Build logic change:  Fix layer stacking issue (CCBCC-Clayton)

It was noted at a site that the layering of a pallet was not correct.  After investigation it appeared the package type did not have a pattern assigned.  This package type was being treated like package types with a pattern assigned.  This caused an issue where higher priority package type layers were being placed lower on the pallet.  In the example below, the package type 78 has the priority 10 (with no palletizer pattern assigned) and package type 20 has the priority 103 (with a palletizer pattern assigned).  Package type 20’s layers should be placed higher but are not.  

Before code change shows the lower priority package type layer is stacked higher:

After the code change, the priority for a package type is applied even if no palletizer pattern is assigned.