...
Detail:
Load Sales Orders AND Load Web Sales Orders services accept a new optional field called "GroupReference". Clients can send us a “GroupReference” with a Sales Order which will be used in the WMS to group orders in a Wave.
...
Summary:
"Push Optix Order" service to support new "GroupReference" field
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
We now push the “GroupReference” field to the "Push Optix Order" service enabling us to use Scriban to map this to the “related_brand_external_identifier” field in the Optix request for specific Optix clients that require this.
...
Summary:
Retrieve CW Documents List - “parentOriginAgentRef“ now optional
...
Detail:
Previously iHub required “parentOriginAgentRef“ when calling the “Retrieve CW Documents List” service. However not all shipments have a parent so this was changed to optional.
...
Summary:
Fix for push messages getting sent twice during busy periods
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Even if two instances try to send the same push message simultaneously, only one instance will actually send the message to prevent the same push message getting sent twice during busy periods.
...
Summary:
Push retry to support 500 Internal Sever Error and delayed last attempt to push
...
Detail:
If a message is not delivered to a client (via FTP or REST), iHub retries to deliver the message (file or request) 3 more times every 15 minutes. If after the third attempt the message cannot be delivered, iHub will wait 60 minutes and try one more time to push. If this also fails then iHub will no longer attempt to push the message.
...
Summary:
Token automatically refreshes after expiration
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Users often have the Activity report open for some time as they monitor incoming transitions. After a period of time if the user tried to move to another part of the application there would be an error as the token would have expired. A fix has now been applied to automatically refresh the token so the user can continue to use the application.
...
Summary:
Ability to filter Activity by specific Optix services
...
Detail:
A fix has been applied to prevent the “error in XML document“ exception users were getting when using the REST Testing Tool to load XML requests.
...
Summary:
Fix for "Export Client Configuration" - Authorization has been denied for this request
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Client Setup → Active Clients
Click on a Client
Click “Export Client Configuration“ button
Previously this would return ““Authorization has been denied for this request.
A fix has been applied for this.
...
Summary:
Push Service Test Tool - Fix for sending push messages without setting any parameters
...
Detail:
Users can now test a Push service by clicking the “Send Message“ button without changing any parameters.
...
Summary:
Fix for application behaviour when clicking Back button on mapping a CSV file
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Fixes applied for the following case:
Case 1:
Go to Settings → Service Settings → Any service and protocol with configurable mappings already set → Edit current mapping and press “Back” button. You will be returned to an incorrect page “Step 2. Provide a sample file”
Case 2:
Go to Settings → Service Settings → Any service and protocol with configurable mappings already set → Map your own CSV file and press “Back” You will be returned onto previous page, but option “Edit current mapping” will disappear
...