Versions Compared

Key

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

Summary:
Authentication with Grey Orange

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-859

Detail:
Support OAuth token based authentication with Grey Orange

...

Summary:
Push Item Master (Grey Orange)

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-860

Detail:
POST Item Master data to a GreyMatter API endpoint and use Scriban to map the payload in the format GreyMatter requires

...

Summary:
Push Item Master Update (Grey Orange)

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-861

Detail:
PUT Item Master data to a GreyMatter API endpoint and use Scriban to map the payload in the format GreyMatter requires

...

Summary:
Push Pick Expectation (Grey Orange)

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-862

Detail:
POST Wave data to a GreyMatter API endpoint and use Scriban to map the payload in the format GreyMatter requires

...

Summary:
Load Tote Association (Grey Orange)

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-863

Detail:
Support for Grey Orange loading Tote Associations using their own payload.
We link these external Plate Numbers (Totes) with our existing internal Plate Numbers.

...

Summary:
Load Wave Pick Complete (Grey Orange)

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-864

Detail:
Support for Grey Orange loading Wave Picks using their own payload.
We batch pick a Wave based on these picks and the complete the Wave.

...

Summary:
CargoWise Version 2 document services

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-884

Detail:
New “v2” version of "Retrieve CW Documents List" and "Retrieve CW Document" services

...

Summary:
Load XUS - support for additional new fields

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-900

Detail:
Load XUS service supports the following new field:

  • “ParentOriginAgentRef“ optional, 20 characters max

  • “DeliveryMode” optional, 4 characters max

  • “ShipmentETAPOD” datetime, optional

  • "ShipmentATAPOD", datetime, optional

  • "ShipmentInlandETA ", datetime, optional

  • "ShipmentInlandATA", datetime, optional

  • "ShipmentATA", datetime, optional

  • "ShipmentCustomsClearedDate", datetime, optional

  • "ShipmentLastFreeDay", datetime, optional

...

Summary:
CSV Mapping - Ability to auto set a string value

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-752

Detail:
You can now auto set a string value when mapping a CSV file. This will allow clients to send the same value every time such as a currency.

...

Summary:
iHub NuGet package now includes package description

...

Detail:
”Indigina.IntegrationHub.ApiClient” NuGet package now includes package description

...

Summary:
Changed to “SqlAzureExecutionStrategy” to retry when transient failures occurs

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-871

Detail:
The SqlAzureExecutionStrategy will retry instantly the first time a transient failure occurs, but will delay longer between each retry until either the max retry limit is exceeded or the total time hits the max delay

...

Summary:
Swich to code based authentication

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-750

Detail:
Changed the authentication scheme to Azure B2C code based authentication. This has decoupled the frontend from backend and made authentication more flexible.

...

Summary:
Activity - "Activity Admin Access" permission to view all activity records as well as 401 unauthorized records

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-916

Detail:
"Activity Admin Access" permission allowing users to access the iHub activity report in a similar way we do with the Admin Panel on our our other applications. Users with access to this permission can view all activity records without iHub retrieving user entitlements and can also view unauthorized items of the Activity report.

...

Summary:
Push Service Test Tool - support for NULL values

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-909

Detail:
Ability to set specific properties to NULL when editing the push message to send

...

Summary:
Added retry when Service Bus is being throttled

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-883

Detail:
Fix for iHub consuming all available IOPS on Push Created messages. A retry policy has been added for this.

...

Summary:
Push Service Filters - Fix so “Save” button is enabled when adding a new filter

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-849

Detail:
Fix applied so “Save” button is automatically enabled as soon as a user adds a new filter.

...

Summary:
UI fix to ensure hidden fields with sensitive data remain hidden

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-825


Detail:
We automatically hide values in textboxes that contain sensitive data. The user can click on these to show the values but there was an issue that these would also be displayed when the user pressed the enter key on another text box. A fix has been applied for this.

...

Summary:
Hide "MainMenu_Support" when opening and logging out of iHub

Ticket:

Jira Legacy
serverSystem JIRA
serverIdb157ffa3-650f-3eac-ac6a-49d6a4f1db87
keyIHUB-899

Detail:
The "MainMenu_Support" menu item is now not displayed when opening and logging out of iHub.

...