6659613 

When using keyless child objects, the SBR duplicates some of the child objects. 

6731913 

The getEUID method throws inappropriate null pointer exceptions. With this fix, getEUID behaves as follows:

• Given a valid facility and LID, getEUID returns the EUID.

• Given a valid facility and invalid LID, getEUID returns null.

• Given a valid facility and an LID that does not match the required format, getEUID throws a validation exception.

• Given an invalid facility, getEUID throws a validation exception.

6699674 

If an identifier that is too long is passed to getEUID, a null pointer exception is thrown instead of a validation exception.

6807758 

You have to modify runed.bat in order to run a Master Index client project.

6718625 

The value of the max-result-size property for EDM reports is being overridden by a default value of 100.

6855160 

From NetBeans, you cannot save changes to the database or configuration files. 

6799090 

After importing a 5.1.3 eView project, the Sun Master Index External Application is not recognized in the client deployment profile. 

6697222 

The Enterprise Data Manager (EDM) does not display fields that contain double-quotes correctly. 

6752758 

Installing Sun Master Patient Index creates multiple eView.Person objects beneath the Master Patient Index projects. 

6747936 

The resolved date for potential duplicates is not stored in the Master Index database. 

6778606 

Serialization of MergeResult and TransactionObject objects does not work when the client is run from a different JVM.

6825113 

The ObjectNode.equals(Object o) method does not take the class into account when comparing objects, resulting in false positives.

6875294 

Master Index has trouble initializing when running with a JRE version 1.5.0_14. 

6875297 

An EJB exception is thrown when trying to create the first record in a master index from the EDM. This occurs with JRE 1.5.0_14. 

6637511 

The cursor is not positioned correctly when a new page on the EDM is displayed. 

Issue 160

Outbound messages from Master Index are missing the create date and update date values. 

Issue 189

The MIDM Audit Log currently displays the create date as a date rather than a timestamp. There can be many transactions within a short period, so a timestamp would be more useful. 

Issue 212

When an address field is added with an apostrophe in the text, the field cannot be edited. 

Issue 219

The banner for the Information dialog box that appears when you tab away from the Edit Source Record window is partially hidden. 

Issue 222

The generated outbound.xsd file is unusable in NetBeans. The following lines were added to address this:

xmlns:tns="uri:PersonOutMsg" targetNamespace="uri:PersonOutMsg"

Issue 229

The transaction reconstruction for Master Index is inefficient. In addition, the timestamp is only to the second, which can lead to an exception when two transactions are processed in the same second. 

Issue 237

The Transaction Detail does not display when the EPath parser finds invalid characters. 

Issue 240

If the same code list is being used for more than one field on the MIDM, then the generated codelist.sql file will contain that code list more than once. This causes an error when running the script.

Issue 255

The update.xsd file that is used to validate update.xml does not allow fields to be specified in the system-fields element in the survivor calculator.

Issue 257

Fields that are defined as not editable can be modified through the Source Record View/Edit window. 

Issue 272

The resolved date for potential duplicates is not stored in the database. 

Issue 278

The outbound JMS message XML does not have a namespace. 

Issue 287

The Clear buttons for child objects on the Source Record window do not work consistently.  

Issue 293

A remote call to the Master Controller EJB fails on merge methods because the result object cannot be instantiated on the client. 

Issue 295

Data enclosed in square brackets cause a validation error in the FieldDescriptor.validate method.

Issue 298

When a field contains data of the type Long, the text covers the next record. To prevent this, Long data fields only display 20 characters. If the field contains more characters, an ellipsis (...) appears at the end of the data. Mousing over the ellipsis displays the full text. 

Issue 304

The generated outbound,xsd file has maxOccurs=”1” for the SBR element. Some transaction types have two SBR elements.

Issue 309

The Print button on the Transactions window does not appear correctly. 

Issue 312

Transaction History on the MIDM does not work correctly with Firefox 2.0.x. 

Issue 322

When the system and local ID are displayed on the Transaction History and Audit pages, the local ID is displayed first. Since the formatting of the local ID is dependent on the selected system, the system field should appear first. 

Issue 324

The MIDM does not allow variable local ID lengths. 

Issue 325

The topic connection is not closed when the EJB call that triggers an outbound message completes, resulting in too many open connections. A processing exception is thrown. 

Issue 332

Non-updateable fields do not appear on the Potential Duplicate report. 

Issue 334

When Master Index generates outbound messages, it includes deleted child objects in the message even though they are flagged as being removed. 

Issue 335

When you clean and build an MDM project, the properties are rest for the corresponding EJB project, which removes any custom changes including the additional of JAR files. The EJB project will no longer compile. 

Issue 341

The error message is not displayed in certain cases of SEQException, so the cause of the exception is not apparent.

Issue 344

The SBYN_MERGE database table should have an index on the merged_euid column. 

6682971 

Range search fields should be arranged more clearly on the MIDM search windows. 

6708211 

A record's history displays incorrectly after an unmerge transaction.  

6710895 

When a record is updated while you are viewing its transaction history on the MIDM, you are not alerted that you are no longer viewing the most current information. 

6858060 

When you enter a field name with more than 20 characters, a message appears warning of an Oracle limitation. This limitation also exists for MySQL databases, but can be removed since MySQL does not have the same limit. 

6700054 

The field labels and field values look too similar on the MIDM Records Detail page.  

6703149 

When you enter an invalid local ID on the Duplicate Records page on the MIDM, an error message appears. When the error message is closed, you cannot click on the local ID field to fix it and the System field is cleared. 

6829621 

A null pointer exception occurs as a result of a multi-threading issue in the Sun Match Engine and on TransactionObjectDB.