What's Fixed in OHMPI 5.0

The following bugs are fixed in this release:

Bug Number	Description
30174930	Broadcast messages were invalid according to the generated xsd. Now broadcast messages successfully validate against the generated xsd.
30360804	The "Unable to find Mbean" message displayed as a severe message, although there is no impact on functionality. Now the message displays as a warning.
30991195	After migration from eIndex 6.3 Database 10.2 to OHMPI v4.0.2.3 Database 12c, before-and-after transactions could not be fetched using the lookupTransaction() webservice call. Now, the lookupTransaction() webservice call can bring up before-and-after transactions.
31862410	If a text field is long and contains a double quote, the tooltip does not display the complete value. Now the complete value displays in the tooltip.
31878404	When executing the Patient Demographics Query (PDQ) by CNS, the query result returns only one row when more records exist. Now the query returns the correct number of records.
32239266	The Patient Demographics Query (PDQ) profile was not able to recognize a mother's name query parameter using the '%' wildcard. Now, the Patient Demographics Query (PDQ) profile recognizes a mother's name query parameter using the '%' wildcard.
32400389	Data entered through the GUI that contained the '&' character resulted in incomplete data getting saved. Now, when the data contains the '&' character, it is correctly processed and saved.
32829992	Update.xsd allows a single parameter for default survivor strategy. Now the file allows multiple parameters for default survivor strategy.
32998579	The SystemField class equals() and hashCode() methods violate the contract in Java when the field value is null. Now, the equals() and hashCode() methods of the SystemField class work properly with a null field value.
Enhancement 32830059	Transaction metadata was not included in broadcast messages. Now, broadcast messages include transaction metadata based on configuration. The master.xml file has a new configuration parameter: include-transaction-metadata. If the value is true, the broadcast message includes transaction metadata. If the value is false, or if the configuration parameter is not present, then the broadcast message does not include metadata.
Enhancement 32830083	Inactive EUIDs were considered while calculating duplicates and matches. Now, the system considers inactive EUIDs while caclulating duplicates and matches based on configuration. The master.xml file contains a new configuration parameter: include-inactive-object-in-matching. When false, inactive EUIDs are not considered while calculating duplicates and matches. If true or not specified, inactive EUIDs are considered while calculating duplicates and matches.
Enhancement 32830101	Release 5.0 has a new API to create an enterprise object (EO) with a specified EUID: createEnterpriseObjectBySystemRecordsAndEUID. The API accepts an array of SystemObjects and an EUID as parameters. If provided a new unique EUID and an array of SystemObjects, the system creates a new EO. If an EUID is not provided with the array of SystemObjects, the system creates a new EO with a new EUID based on the sequence number. If provided with an existing EUID, the API throws an error message.
Enhancement 32830108	EUID SystemObjects were not displayed in a particular order in the UI. Now, the UI displays SystemObjects of an EnterpriseObject ordered first by SystemCode and then LID.