Summary:
Add Partner support to iHubPush Optix Order
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
iHub accepts data from Seko360 and then calls an external system (Optix) to create an order. The data is mapped in the format required by Optix.
Optix returns a response that contains a unique “id“ for the Order that was created in their system. This “id” is sent back to Optix when the “Push Optix Shipment” service is called.
...
Summary:
Push Optix Shipment
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
iHub accepts data from Seko 360 and then call an external system (Optix) to create a shipment. The data is mapped in the format required by Optix.
Optix returns a response that contains a unique “id“ for the Shipment that was created in their system.
...
Summary:
CSV Mapping - Transformation modal to set Formatting, Validators and Transform
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
New “Transformation” column (to replace the existing Formatting and Validators columns) when mapping a CSV file. Allows users to click a “+“ icon to add a new transformation or a “pencil” icon to edit any existing transformations which opens a new modal window.
In addition users can apply a Scriban transformation to a field.
E.G
| Code Block |
|---|
{{ value | string.downcase == "true" ? "DDP" : "DDU" }} |
...
Summary:
Push Service Filters - Support multiple Values (OR instead of AND)
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Clients have the ability to apply multiple “Filters” to REST and FTP service protocols. Only messages that match these “Filters” are sent. Previously filters worked on an “AND” basis. This has now been changed so we support filters on an “OR” basis. Press the enter key when setting the “Comparison Values“.
...
Summary:
Migration to Azure SignalR
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Switched to using Azure SignalR supporting bi-directional communication between the server and client. This has allowed us to overcome some of the intermittent issues we were experiencing with our previous SignalR implementation
...
Summary:
Load Sales Order Cancellations - Support for order numbers ending with a period
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Fix applied so clients can call the “Load Sales Order Cancellations“ service and specify a period at the end of the “SalesOrderNumber“.
...
Summary:
Support for Partners / Tenants
Tickets:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Ability to split data by tenants (Partners).
This allows us to optimise queries with filtering by a partner and also restrict user access.
...
Summary:
Migrated to workspace-based Application Insights
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
New capabilities:
Customer Managed Keys. You can encrypt all data with encryption keys that you have access to.
Private Link support.
Capacity Reservation tiers help save on cost.
Faster data ingestion with Log Analytics streaming ingestion.
...
Summary:
Fix for unsubscribing from Push Services
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Detail:
Fix applied to the unsubscribe mechanism to ensure clients are unsubscribed from Push services when they no longer require these.
...