Resolved Issues: Calyx RIM 6.2 CHF 5
The following issues that were reported to Technical Support have been resolved. Issues are listed in descending order by their internal tracking numbers. Customer incident numbers that were recorded when the issues were reported are included in brackets following the internal tracking number.
Calyx RIM 6.2 CHF 5 resolves the following issues.
| Issue | Build | Hotfix Build | Description |
|---|---|---|---|
| 26608;
[INC0038408] |
6.2.0.5.0055 | N/A | After migrating to Calyx RIM 6.2 CHF 4, clicking the Concerned Parties icon resulted in an error. This occurred if the domain of a user was changed and there was a NULL value for that user in the Domain column in the SEC.USR table. This issue is resolved. |
| 26606;
[INC0038763] |
6.2.0.5.0055 | N/A | The Submission Readiness report took a longer time to generate than usual and in some instances the report failed to generate. This issue is resolved. Now, the Submission Readiness report generates successfully and with less time. |
| 26597 | 6.2.0.5.0055 | 6.2.0.4.0.0111 | When EAEU submissions were published after performing a Delete operation on one or more leafs, incorrect leaf attributes and DocID values were included in the output XML. This issue is resolved. |
| 26592 | 6.2.0.5.0055 | 6.2.0.4.0.0110 | The Export Published Output process did not support Cyrillic symbols in filenames when choosing to embed PDF files into the EAEU XML file. This issue is resolved. |
| 26588 | 6.2.0.5.0055 | 6.2.0.4.0.0110 | The Export Published Output process failed intermittently when choosing to embed PDF files into the EAEU XML file when the processed file path included spaces. This issue is resolved. |
| 26583;
[INC0023438] |
6.2.0.5.0055 | 6.2.0.4.0.0110 | If a workflow was associated to the assembly root, a folder, or a document in an initial sequence assembly, and the Synchronize with the Submitted View option was applied, the workflow was lost. This issue is resolved. Associated workflows are kept for each node after the option is applied. |
| 26582 | 6.2.0.5.0055 | 6.2.0.4.0.0110 | The mediaTypeCode attribute was missing from the embedded PDF nodes of the EAEU XML output file. Although this attribute is not required per the schema, the agency validator requires it. This issue is resolved. The mediaTypeCode attribute is now included in the EAEU XML file for embedded PDF nodes. |
| 26574 | 6.2.0.5.0055 | 6.2.0.4.0104 | When an EAEU submission was published, the name of the XML index file generated was incorrect. This issue is resolved. Now, the XML index file includes the correct name: index-r-022.xml |
| 26571 | 6.2.0.5.0055 | 6.2.0.4.0104 | The incorrect codeListId value was generated in the UnifiedCountryCode of an EAEU assembly published XML. This issue is resolved. |
| 26565;
[INC0033560] |
6.2.0.5.0055 | 6.2.0.4.0106 | Calyx RIM did not recognize some users as members of their assigned Active Directory (AD) groups. This issue is resolved. |
| 26556;
[INC0033264] |
6.2.0.5.0055 | At times, the Synchronize with the Submitted View option took more time than usual. This issue is resolved. | |
| 26537;
[INC0030024, INC0033088] |
6.2.0.5.0055 | N/A | If an assembly root was not selected during publishing, variables failed to be resolved in the submission output for all the leafs. This issue is resolved. |
| 26533;
[INC0029832] |
6.2.0.5.0055 | 6.2.0.4.0104 | Errors were found when the Publishing Readiness Query was run for the China eCTD. This issue is resolved. |
| 26530;
[INC0029543] |
6.2.0.5.0055 | 6.2.0.4.0104 | The Document Creation Date displayed the current date, even though no value was specified for that field in the modify mode. This issue is resolved. Now, Document Creation Date displays a date only when the field is populated. |
| 26528;
[INC0029467] |
6.2.0.5.0055 | 6.2.0.4.0104 | When creating and publishing an assembly with the new EAEU Assembly Template including section 2.7.3, the following message appeared: "WARN : The characters: ? were removed from the path"." This issue is resolved. |
| 26527, 26226, 25965;
[INC0029460, 00064445] |
6.2.0.5.0055 | N/A | The options For this Element and Document were not available on the Update Overlay Settings page invoked from the Document. This issue is resolved. |
| 26507 | 6.2.0.5.0055 | 6.2.0.4.0104 | The EAEU 1.0 assembly template is updated and now eCTD is used as the assembly type. |
| 26504 | 6.2.0.5.0055 | 6.2.0.4.0093 | A Vertical Privilege Escalation (Systemic) vulnerability was reported as a result of penetration testing. This issue is resolved. |
| 26502;
[INC0025226] |
6.2.0.5.0055 | N/A | Applying the eCTD Import to an AU-3-0 assembly where the Sequence Description attribute had a code values different from those provided by the agency caused the import to fail. This issue is resolved. Now the import ignores the mismatches and takes the code value. |
| 26491 | 6.2.0.5.0055 | 6.2.0.4.0096 | When using Mass Update Properties with the Update and Preserve option selected to set the extension value for leafs in a folder, the extended attributes were erased for child folders or leafs within the selected range. This issue is resolved. |
| 26487;
[INC0024292] |
6.2.0.5.0055 | N/A | After importing published GCC submissions, some folders were renamed or missing. This issue is resolved. Now, the imported assembly keeps the original structure. |
| 26486;
[INC0024081] |
6.2.0.5.0055 | N/A | If an application had an Active or Not Approved or Withdrawn status, and the application had a registration with a status other than Withdrawn, it was not possible to update an event with Withdrawn status. This issue is resolved. |
| 26469;
[INC0023438] |
6.2.0.5.0055 | N/A | If a Workflow was associated to a leaf in an initial sequence assembly and the Synchronize with the Submitted View option was applied, the Workflow was lost. This issue is resolved. Associated Workflows are kept for each leaf after the option is applied. |
| 26458;
[INC0022479] |
6.2.0.5.0055 | 6.2.0.4.0106 | Publishing failed for the 2.3.S, 2.3.P, and 2.7.3 folders of ICH Module 2-5 v3.2 when the metadata field contained a single quote character. This issue is resolved. |
| 26455;
[INC0022252] |
6.2.0.5.0055 | N/A | Variables with spaces in the Variable Name field did not resolve in the published output. This issue is resolved. |
| 26449 | 6.2.0.5.0055 | N/A | An InSight API request to retrieve a list of assemblies for assembly types other than templates did not work. This issue is resolved. |
| 26446 | 6.2.0.5.0055 | N/A | When using the Mass Update Properties functionality, the time taken for updating the extended attributes was longer than the time taken for the common attributes. This issue is resolved. |
| 26444;
[INC0021105] |
6.2.0.5.0055 | N/A | Incorrect Folder/Leaf names were observed in sections 1.08, 1.09, and 1.12 in JP eCTD Module 1 v1.0 assembly template. This issue is resolved. The JP eCTD Module 1 v1.0 assembly template is updated. |
| 26439;
[INC0020399] |
6.2.0.5.0055 | N/A | For an eCTD Import, the “Waiting for InSight” status appeared without updates in Job Status. There was no indication that the import failed when the imported submission had a sequence that failed to lifecycle due to mismatched Folder Types. This issue is resolved. "Completed" appears in the Job Status column, and the sequence is indicated. When the m1-us-form type folder is imported into submission with the Submitted view and m1-us-admin-form type folder is imported into submission with the Sequence view, the Node type mismatch is found: a node with m1-us-admin-form type replaced a node with m1-us-form type in the Submitted View. message appears. |
| 26434;
[INC0020054] |
6.2.0.5.0055 | N/A | In Internet Explorer, when using the Delete (Withdraw) option on multiple leafs from subfolders of a Working assembly, the process ran would spin for a long time with no result. This issue is resolved. The method used to communicate with the server is changed and now you can select any number of leafs to withdraw. |
| 26432;
[INC0019888] |
6.2.0.5.0055 | N/A | If it was associated to a Product and Project, an Event could not be updated using the API . This issue is resolved. |
| 26425;
[INC0376737] |
6.2.0.5.0055 | N/A | In a Working assembly with documents assigned from Documentum, the links created to bookmarks in other documents using Calyx RIM Linking plug-in (PDF) resolved to incorrect pages after publishing. This issue is resolved. |
| 26402;
[INC0017878] |
6.2.0.5.0055 | N/A | When an event was closed with a reason using the Specify Reason for Termination/Withdrawal option, the same reason was applied to the parent application. This issue is resolved. |
| 26401;
[INC0017630] |
6.2.0.5.0055 | N/A | When deleting leafs in bulk using Delete (Withdraw) lifecycle operation in the Working assembly, the assembly tree refreshed and the deletion symbol (crossed leaf) appeared only on one of the leafs instead of all of them. This issue is resolved. |
| 26397, 24517;
[INC0017263, 00044443] |
6.2.0.5.0055 | N/A | When deleting an assembly, there was no indicator of the deletion in progress. This issue is resolved. A progress indicator shows that the deletion is in progress. |
| 26370;
[INC0015274] |
6.2.0.5.0055 | N/A | The pagination formulas using Reverse and Bates types did not resolve properly for paper publishing. Example:$Bates($Reverse($Calculate(${ATP}-${ARP}+1),"-1"),5).
This issue is resolved. The formula works when an intermediate variable is used as the first one in alphabetical order according to Variable Code. Example:
|
| 26346;
[INC0014465] |
6.2.0.5.0055 | N/A | Notifications were not sent even when the mail-service.xml file included a valid SMTP server name and port number. This issue is resolved. |
| 26340;
[INC0014300] |
6.2.0.5.0055 | N/A | After reordering leafs in a Working Assembly using Reorder Child Leafs option, users observed empty folders in Publishing and Sequence views. This issue is resolved in Calyx RIM 6.2 CHF 4 as a result of other fixes. |
| 26310, 19440;
[INC0012460] |
6.2.0.5.0055 | N/A | After performing a DMS Synchronization on an assembly with an assigned document that was versioned, the document attributes and assembly tree were not automatically refreshed by Calyx RIM. This issue is resolved. Now, the icon 'Newer version available' is displayed without having to manually refresh the assembly tree. |
| 26276;
[INC0011104] |
6.2.0.5.0055 | N/A | The Assembly templates for CH 1.3 and CH 1.4 contained errors that lead to validation issues. This issue is resolved. |
| 26221;
[00064631] |
6.2.0.5.0055 | N/A | In EU Submissions with MAA in Submission Type and with the initial value in Submission Unit Type, the users were able to save the empty INN in EMA Envelope Information. This issue is resolved. Now, the users are required to populate it when needed. |
| 25831 | 6.2.0.5.0055 | N/A | When using the Calyx RIM API to convert a leaf to reference, it could not be targeted to a leaf from a Sequence view. This issue is resolved. |
| 25487;
[00055381] |
6.2.0.5.0055 | N/A | The Find and Replace option did not function as expected in the Publishing view of an assembly and was not available for the folders with new or lifecycle-operated nodes in the current sequence in the Working view. This issue is resolved. Now, in the Publishing view, the Find and Replace option covers the leafs and documents and is available for folders with new or lifecycle-operated nodes in the current sequence in the Working view. |
| 25325;
[00053635, 00055122, 00059463, 00062975,INC0016253, INC0016254, INC0017802] |
6.2.0.5.0055 | N/A | A GCC valid submission with the language missing failed to import from eCTD. This issue is resolved. Now, the eCTD import is completed with no errors in the Job Requests even if there is no information about the language. The system uses English as the default language, and the language folder name is the same as in the GCC template. |
| 25263;
[00052834] |
6.2.0.5.0055 | N/A | GCC submissions containing multiple Cover Letters could not be imported to Calyx RIM. This issue is resolved. |
| 23864; [00039884, 00054020, 00055522, INC0016252] | 6.2.0.5.0055 | N/A | Using the Change Submittal Status wizard after changing a folder extension in a later sequence caused a reference error. This issue is resolved. |