...
Summary:
Wave Configurations - Support for Group Reference“Group Reference”
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Ability to create Client Wave Configurations and set a “Group Reference”. This will give users the ability to use “Group Reference” to group dispatches into a Wave.
...
Summary:
Wave Pick Release - Support for “Group Reference”
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Wave Pick Release process now supports the new “GroupReference” field.
Users can now release waves grouped by the “Group Reference” set in the Client Wave Configuration.
...
Summary:
Dispatch "To Be Packed" - Support for “Group Reference”
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
The “To Be Packed” tab on the “Dispatch List” now support the new “Group Reference” field. Users can use the filter above the grid to filter the results by “Group Reference”.
...
Summary:
Dispatch Detail now displays the "Group Reference" field
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Dispatch Detail view displays the "Group Reference" field.
...
Summary:
Manifesting Schedule - Only set run dates if "CleanSweepRequired" set to True
...
Detail:
When going back to the main “Manifest Access” grid, the filters applied are now maintained. Previously the filters and paging was lost and the user would need to apply the filters again
...
Summary:
Dispatch Update - Fix for default sorts being removed and code refactoring on Dispatch module
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Logistics → Dispatch → Dispatch Update
Click Search
Remove default sorts
Previously we would get a 500 (Internal Server Error) but a fix has now been applied.
...