/
Standardizing Service Field Values for Connected Hotel Interfaces

Standardizing Service Field Values for Connected Hotel Interfaces

Knowledgebase Article: Standardizing Service Field Values for Connected Hotel Interfaces

Overview

When integrating with external hotel interfaces (such as HBSi, SynXis, etc.), Softrip retrieves various service fields (e.g., Designator/“DESIG”) via API. Historically, the values returned for these fields—especially DESIG—have been inconsistent, leading to confusion in downstream processes and customer-facing documents. This article outlines the new approach for standardizing these fields by allowing the system to pull values from internal Softrip service setups instead of relying solely on interface data.

Problem Statement

  • Inconsistent Field Values: External interfaces may return DESIG values that do not accurately reflect the accommodation type or booking context (e.g., a two-bedroom suite showing as “1 Single”).

  • Operational Impact: Inconsistent or misleading field values can cause confusion for users and impact reporting, documentation, and customer experience.

Solution Summary

Softrip now supports a configuration that allows specific service fields (such as DESIG) to be sourced from internal service setups rather than the interface response. This ensures consistency and allows for more generic, predictable values (e.g., always displaying “Room” instead of a supplier-specific designation).

Key Features

  • System Default Configuration:

    • Add a new Default in system settings:
      UseInternalServiceInfoForInterface-[ContractThru]
      (e.g., UseInternalServiceInfoForInterface-HBSI, UseInternalServiceInfoForInterface-SYN)

    • The DefaultText is a comma-separated list of fields to override (e.g., DESIG).

  • Flexible Field Selection:

    • Currently supports overriding DESIG, with the ability to add more fields in the future.

  • Mask-Based Mapping:

    • Internal service setups can map DESIG values to specific passenger masks (e.g., A, AA, AAA, etc.).

  • Consistent Display:

    • Overridden values are displayed consistently in carts, documents, and downstream processes.

Setup Instructions

1. Configure System Default

Add a new Default in the system settings. Example SQL:

insert into Defaults Values ('USEINTERNALSERVICEINFOFORINTERFACE-HBSI',  'Use internally loaded content as opposed to content from HBSI.', 'DESIG', 'stadmin', GetDate())

  • Replace HBSI with the appropriate interface code as needed.

  • The DefaultText can include multiple fields, separated by commas.

2. Service Setup

  • For each relevant service, configure the desired DESIG value in the internal service setup.

  • If using mask-based mapping, ensure all relevant masks (e.g., A/AA/AAA/AAAA/AAC) are configured with the appropriate DESIG value.

image-20250918-150713.png

3. System Behavior

  • If the Default is not configured:
    The system uses the interface-provided DESIG as-is.

  • If the Default exists but DefaultText is empty:
    No fields are overridden; system behaves as if the Default is not configured.

  • If the Default exists and includes DESIG:
    The system pulls DESIG from the internal service setup and displays it consistently.

  • If a mask is not mapped internally:
    The system falls back to the interface-provided DESIG for that mask.

image-20250918-151252.png

Acceptance Criteria

  • Only the fields listed in the DefaultText are overridden.

  • Existing reservations are updated to use the new logic if repriced or re-shopped after the Default is configured.

  • Downstream processes and documents reflect the standardized values.

Additional Notes

  • This configuration is intended for customers transitioning to the new approach. Do not enable for customers who require interface-provided values unless specifically requested.

  • The process will be tested as part of customer transitions from legacy to new interfaces.

  • For related configuration options (e.g., “CLEARDESIG”), see https://softrip.atlassian.net/browse/SSM-12171.

References

Frequently Asked Questions

Q: What happens if a new mask is added but not mapped internally?
A: The system will use the interface-provided value for any unmapped masks.

Q: Can this be used for fields other than DESIG?
A: Yes, the DefaultText can include additional fields as needed.

Q: Will this affect existing reservations?
A: Only if the reservation is repriced or re-shopped after the Default is configured.