Custom Input Mapping Error For Disk-Based Rating When Input Data Contains Ampersand Character

(Doc ID 2185267.1)

Last updated on JUNE 20, 2017

Applies to:

Oracle Insurance Insbridge Rating and Underwriting - Version 5.0.1 and later
Information in this document applies to any platform.


On : Insbridge 5.0.1 version, SoftRater Engine

Customer is encountering an input mapping transformation error on any disk-based rating transactions (i.e. submitted with the ProcessRequestCustomFromDisk operation) that contain a properly encoded ampersand character in the input data, e.g.:


This error is being written to the XML as straight text into the output file (i.e. not in an XML element), thus the output file is not well-formed XML.

These same transactions process without error if rated with the input XML submitted via the message payload, e.g. submitted with the ProcessCustom operation. Both rating scenarios are using the same custom .XLST, so the same (error-free) results are expected whether rating from disk or message payload.

----------------------- Mon Sep 12 10:30:41 MDT 2016: Custom Input Transformation error. Template name: C:\Insbridge\environments\IBSS-WAS\XXX\SR\Custom\HorizonInputXMLTranslation.xsltThe entity name must immediately follow the '&' in the entity reference.

The issue has the following business impact:
Due to this issue, users cannot rate when an ampersand is encountered in a test XML input file.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms