Resolved Issues: Calyx RIM Viewing 5.5

Calyx RIM Viewing 5.5 resolved the following issues:

Issue

Description

1396; [00053952] Calyx RIM Viewing failed to send e-mail notifications to users when applications were registered via asynchronous registration. This issue is resolved.
1394; [00053743, 00053911, 00053670, 00054793] A user was unable to open documents that had "%" (percentage) character in the document content. This issue is resolved.
1390; [00053289] When long names were used for the M5 3.5.1 folder, resizing the TOC window wrapped the names over itself and made them illegible. This issue is resolved.
1389; [00053246] When using the Submission Navigator filter, the values in the fields were not displayed. This issue is resolved.
1384; [00052782] The Data Exchange configuration failed to notify the status changes in Calyx RIM Viewing. This issue is resolved.
1383; [00052789] For EU DTD 3.0.1 submissions, the Identifier, Tracking Number and Submission Unit values were not displayed on the Administrative Information window. This issue has been resolved.
1377; [00052473] After upgrading to Calyx RIM Viewing 5.4 CHF 5, users with administrator privileges were unable to log on because Calyx RIM Viewing failed to get user roles from Active directory. There were also performance issues while logging on to Calyx RIM Viewing. These issues are resolved by the new timeOut and enableSubgroupsLookup parameters that are added to the LDAPConfig.xml file which is included in this release.
Note: All LDAP connections must be first remapped while in the database mode after performing the server upgrade procedure.
1373; [00051730] The performance issue experienced in Navigator when switching between views for different sequences has been addressed in this release.
1347; [00050156] It was not possible to change the submission status of sequences in an application. This issue is resolved.
1113; [00037291] When no entry in the SubmissionStatus.xml file was set to active="false", an error was displayed in the Navigator window. This issue is resolved.