Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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:
Push retry to support 500 Internal Sever Error and delayed last attempt to push

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keySHUB-844

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:
Ability to filter Activity by specific Optix services

...

Detail:
We often push a number of messages in a group. Users now have the ability to click on the “Outgoing Messages” tab and filter these by searching for a specific term. Previously when a user searched for a message, it would automatically expand. A fix has now been applied so messages remain neatly in a collapsed state.

...

Summary:
REST Testing Tool - Fix for error when sending XML requests

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keySHUB-942

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:
Push Service Test Tool - Fix for sending push messages without setting any parameters

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keySHUB-940

Detail:
Users can now test a Push service by clicking the “Send Message“ button without changing any parameters.

...