Summary:
Wave Picking Bots - Load Tote Association
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Support Grey Orange loading Tote Associations into the WMS Wave Picking module
...
Summary:
Wave Picking Bots - Load Wave Pick Complete
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Support Grey Orange loading Wave Picks into the WMS Wave Picking module
...
Summary:
Auto set BBD and Lot No on "Move Stock by Location"
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
We now auto set the BBD and Lot Not when using the “Move Stock by Location” module and there is only one active licence plate with a quantity greater than zero in the From Location for the scanned SKU.
...
Summary:
Wholesale and Retail dispatches for clients enabled for Wave Picking can now be picked using the “Fast Dispatch” module on the mobile device
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Mobile → Fast Dispatch: Users now have the ability to pick Wholesale and Retail dispatches for clients that are enabled to use wave picking.
...
Summary:
Optix - Added support for Rotterdam 1 and 2 DC's
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Added support for pushing Optix data for Rotterdam 1 and 2 DC's
...
Summary:
Counting - Fix for user entering an invalid Count Quantity
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Extra validation added to prevent users incorrectly entering an invalid count quantity. This can happen when a user scans a barcode by mistake instead of entering a count quantity.
...
Summary:
Dispatch Box Type - Store exact weight and UOM captured by user before applying any conversions
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
We now capture the exact weight and UOM set by a user when creating a new Dispatch Box Type.
Previously we would store all weights in one UOM (KG) and apply conversions to the required weight UOM when required.
...
Summary:
Improved performance of Company Filter in User Management
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Performance improvement applied to the Company Filter in User Management providing a faster user experience.
...
Summary:
Retrieve what clients a DC user has access to ("UserCompany" access Phase 3)
...
Detail:
Updated existing modules to check what companies a user has access to.
...
Summary:
Dispatch Detail Report - Fix for filtering by Client
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Fix applied to the “Dispatch Detail” report so users can filter this grid by Client.
...
Summary:
Push Optix Shipments - Exclude full short shipments
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Exclude pushing data for dispatches that have been fully short shipped so that we are not pushing empty parcels that get rejected by Optix.
...
Summary:
Check if "CleanSweepRequired" after packing otherwise change status to "Dispatched"
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
After Pack Complete:
If "CleanSweepRequired" is True then the dispatch remains at “To Dispatch” until the manifest is run.
If "CleanSweepRequired" is False then the dispatch is automatically changed to “Dispatched”.
...
Summary:
Dispatch Box List - Max 12 weeks date range
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Users can only ever do a max 12 week search period at any given time to limit the amount of data returned especially on live. We have also improved the query that returns the data.
...