Summary:
Global-e - Ability to configure by Partner / Carrier / Client (Integration supports Multiple versions)
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
We now support multiple integration versions with Global-e like we do with Royal Mail and Hermes were you can set a Provider Version.
Pretty Green - V1
Violette_FR - V2
...
Summary:
Global-e - V2 Integration
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
The client sets the “SalesInvoiceNumber“ field on “Load Sales Orders” service on iHub to have the “OrderId” value required by GlobalE.
This will value will then be passed into the TMS Request in the “salesInvoiceNumber“.
Order/GetOrdersDetails
Returns a list of orders details.
Order/GetShippingDocuments
Pass in the OrderId AND the parcel data
Returns the documents in the response.
GlobalE V2 requires manifesting. It works in a similar way to manifesting on Omni Parcel where the TMS stores the shipments to be manifested for the current day.
...
Summary:
IOSS Number - Support for all "Ship From" companies
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Support for sending the “IOSS Number” for all “Ship From” countries when shipping to “Mainland UK“, “Northern Ireland” or the “European Union“
...
Summary:
Reporting Microservice
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Detail:
In the Activity report, when viewing JSON or XML and clicking the “Copy to clipboard” option it now include line breaks to improve readability
...
Summary:
Manifest Document URL now points to the TMS files instead of blob storage
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Previously the manifest document pointed to the blob storage URL. This has now changed to point to the TMS files.
...
Summary:
Integration Partners - Managed by Admin Users only
...
Detail:
Order Types are now managed by Admin users only. This data is maintained in one place and available to all partners.
...
Summary:
More descriptive message displayed when there is no response received from a Carrier
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
A more descriptive message displayed in the Activity logs when there is no response received from a Carrier. Previously it would display “A task was canceled”.
...
Summary:
Activity - Client filter now has Select All and Select None options
...
Detail:
Client filter on the Activity report now supports “Select All“ and “Select None” options making it much easier to filter records on the Activity report.
...
Summary:
TMS Admin - Activity results correctly filtered by Carrier Provider
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Fix applied so Activity results are correctly filtered by the selected Carrier Provider(s). Previously there was an issue when users filtered by DHL.
...
Summary:
UI - Same loading icon used by Admin and Partner users
...