Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Summary:
Push Optix Order

Ticket:
IHUB-784 - Getting issue details... STATUS

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:
IHUB-786 - Getting issue details... STATUS

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:
Support for Partners / Tenants

Tickets:
IHUB-775 - Getting issue details... STATUS

IHUB-777 - Getting issue details... STATUS

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:
IHUB-771 - Getting issue details... STATUS

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:
IHUB-819 - Getting issue details... STATUS

Detail:
Fix applied to the unsubscribe mechanism to ensure clients are unsubscribed from Push services when they no longer require these.


  • No labels