Table of contents:



Consignee Master Validation for the Representative and Secondary User Email Duplication

Platform: Shipper Web App

Description:

Validation has been added in the Consignee Master to restrict duplicate usage of the same email ID across the Representative Email and Secondary User Email fields.

With this enhancement:

  • The system blocks saving or updating a consignee when both emails are the same.
  • Cross-consignee validation ensures that within the same ePOD group, an email cannot be used as the Representative Email for one consignee and a Secondary User Email for another.
  • Once an email is saved as a Secondary User Email, it cannot later be edited and reused as a Representative/Primary Email.
  • These validations are enforced across create, edit, and bulk upload flows to maintain data consistency.

Why This Matters:

  • Prevents POD upload failures.
  • Ensures clean and consistent consignee master data.
  • Avoids cascading issues across shared ePOD groups.
  • Multiple duplicate notification emails will be reduced.
  • Improves system stability and reduces operational rework.


Audit Logging for User Master Actions via Integration

Description:

User Master audit logging has been enhanced to include activities performed via integrations/APIs. All user-related actions triggered through integration flows are now captured as part of the audit trail, ensuring complete visibility into how user records are created and managed across systems.

With this enhancement:

  • A new audit type category for Integration Events is added under User Master.
  • Audit logs are captured for Create, Update, Activate, and Deactivate user actions performed via integration.
  • Each audit entry records the event type, timestamp, user identifier (ID/Email), integration source or API identifier, response status, and error details (if any).
  • Integration audit logs are visible in the existing audit screen.
  • No changes are made to the current UI/UX.

Why This Matters:

  • Provides end-to-end traceability for user changes across integrated systems.
  • Eliminates audit gaps caused by API-driven updates.
  • Simplifies troubleshooting by capturing integration errors in audit history.
  • Strengthens compliance, accountability, and operational transparency.


SSO Login Label Updated Based on Configured Provider

Platform: Shipper Web App

Description:

The SSO login experience has been enhanced to dynamically reflect the configured identity provider.

Instead of using a fixed label, the SSO image/icon now changes based on the actual SSO provider configured for the client.

With this enhancement:

  • The SSO login image is rendered dynamically based on the identity provider.
  • Clients using different SSO partners see the appropriate provider-specific visual indicator.

Why This Matters:

  • Reduces confusion caused by incorrect or generic SSO representation.
  • Improves clarity for end users accessing the platform via SSO.


Hover Tooltips for Optima Input, Output, and Retain Pages

Platform: Shipper Web App

Description:

Hover tooltips have been added to clearly identify the Input, Output, and Retain pages in Optima. When users hover over the respective icons, the corresponding page name is displayed, making navigation more intuitive and user-friendly.

With this enhancement:

  • Hovering over the Input icon displays “Input”.
  • Hovering over the Output icon displays “Output”.
  • Hovering over the Retain icon displays “Retain”.

Why This Matters:

  • Improves discoverability and clarity of Optima pages.
  • Reduces user confusion during navigation.


Transit Days Column added in Optima Output Export

Platform: Shipper Web App

Description:

The Optima output export has been enhanced to include Transit Days, ensuring alignment between the UI and the exported data.

This allows planners using EDD and cost-based optimisation to access all critical planning inputs directly from the export file.

With this enhancement:

  • A new column titled “Transit Days” has been added to the Optima output export.
  • The column displays the same Transit Days value currently shown in the Optima output UI.
  • The Transit Days column is positioned next to the existing Dispatch Date column in the export file.

Why This Matters:

  • Ensures consistency between Optima UI and exported data.
  • Supports accurate EDD-based planning and analysis.
  • Eliminates the need for manual reconciliation of Transit Days information.


Optima Output Export - "Ship-to Name" and "Drop-off City" fields in the Materials List tab.

Platform: Shipper Web App

Description:

  • The Optima output export has been enhanced to improve visibility of delivery details within the Materials List tab.
  • Key consignee and location information is now directly available where planners review material-level data.

With this enhancement:

  • Two new columns, “Ship-to Name” and “Drop-off City” are added to the Materials List tab.
  • These columns are positioned next to the existing “shipTo or soldTo” column for better contextual mapping.
  • The values are populated using existing data already available in the export Cover Page:
    • Consignees → Ship-to Name
    • City → Drop-off City

Why This Matters:

  • Improves visibility of consignee and destination details at the material level.
  • Reduces dependency on cross-referencing other sections of the export file.
  • Minimises manual effort and potential errors during shipment planning.


Transporter Performance Data Report Enhancement.

Platforms: Shipper Web App

Description:

  • The Transporter Performance Report has been enhanced to provide indent-level visibility in addition to the existing transporter-level summary. 
  • A new sheet has been added to the report export, allowing operations teams to analyse performance metrics at the individual indent level while retaining the current summary view.

With this enhancement:

  • The report export now contains two sheets:
    • Transporter Performance: Existing transporter-level summary (unchanged).
    • Indent Level Performance: New sheet with one row per indent.
  • Indent-level data includes relevant performance and status metrics aligned with existing SLA logic.
  • Performance metrics at the indent level roll up accurately to the transporter-level summary.
  • Both sheets are generated together as part of the same report export.

Why This Matters:

  • Enables root-cause analysis of delays and failures at the indent level.
  • Helps validate SLA adherence for individual shipments.
  • Improves transparency by allowing cross-verification of summary metrics with raw indent data.