4 Resolved Issues

This section lists issues resolved in this release.

JIRA # Cloud and On-Premise Description
HOPCS-90384 Cloud and On-Premise OFIS Core now evaluates the configured FLIP_PARTNER_RULE and the fiscal partner in the payload when selecting a delivery target. This helps ensure that fiscal payloads are sent to the appropriate partner when multiple fiscal partners are configured for a property.
HOPCS-90784 On-Premise

This update improves reliability and helps prevent data issues during SNRHOS V2 integration.

  • Prevents system errors when the API does not return a response.
  • Ensures that reservation IDs are preserved and sent correctly.
  • Improves request-format validation to help prevent unexpected failures.

The following messages provide clearer error information:

  • SNRHOS V2 Timeout: No response received from the API.
  • Invalid PrimaryKey format. Expected: ModuleName;ActionId;ResvNameId.Received: {x}.

These improvements reduce integration failures and help users troubleshoot issues more quickly.
HOPCS-92785 On-Premise SNRHOS v2 checkout fiscal delivery prevents invalid empty guest entries and transformation failures when accompanying guests do not have a resort mapping during checkout payload generation.
HOPCS-93269 Cloud and On-Premise

OFIS Delivery uses the Fiscal Timeout Period configured in OPERA Cloud or OPERA 5.

  • OPERA Cloud: Administration > Enterprise > OPERA Controls > Cashiering > Fiscal Folio Printing > Fiscal Timeout Period
  • OPERA 5: Configuration > Setup > Application Parameters > Cashiering > Settings > Fiscal Timeout Period

It provides clearer OPERA messages when Generic partner delivery times out or returns an invalid or empty response.
HOPCS-92236 Cloud and On-Premise OFIS Cloud refreshes outbound proxy details when the proxy configuration changes. This helps maintain reliable fiscal delivery communication with external partners.