Calyx RIM 7.2.5 Release Notes

Resolved Issues: Calyx RIM 7.2.5

The following issues that were reported to Technical Support have been resolved. Issues are listed in descending order by their tracking numbers. Customer incident numbers that were recorded when the issues were reported are included in brackets [#####] following the tracking number.

If an issue was resolved in a hotfix before the release, the hotfix build number is included in the table.

Registrations


Issue	Build Number	Description
DE30204; [INC0229723]	N/A	Trying to associate 1000+ products to the Registration resulted in the "Invalid reference" error. This issue is resolved. Now, the products are associated successfully.
DE30162; [INC0226907]	N/A	Trying to view a Product Family with 25000+ products in the UI took longer than expected. This issue is resolved.
DE29739	N/A	Using Major Update or Amendment under Wizards > Create Submission for the applications without products resulted in an error. This issue is resolved. Now, these options work correctly for applications without products.
DE29738	N/A	When performing the API Post request, if Write access was set for Product Family/Product Rights, it was not possible to delete a product family without child entities. This issue is resolved. Now, product families can be successfully deleted.
DE29653; [INC0168860]	N/A	In a Registration, when the Full Product Presentation wizard was used to copy its attributes, the package description was duplicated. This issue is resolved.
DE29642	N/A	After entering the search criteria in the Update Applications wizard and clicking Next, the Select Applications page contained two rows for one application with discrepancy in the Region Type and Region values. This issue is resolved. Now, this page contains one row for one application.

Administration


Issue	Build Number	Description
DE28576	N/A	To retrieve results from the queries List of RMS Fields and List of OMS Fields, a DA List Name was required to be selected from the required field Associated DA List Name. This issue is resolved as the Associated DA List Name is no longer required. It is now possible to retrieve RMS and OMS values regardless of Data Administration list association.
DE28186; [TASK0042598]	N/A	After mapping SPOR Terms to Calyx RIM, RMS terms that had NULLIFIED or NON_CURRENT status were replicated. This issue is resolved. Now, RMS terms are not replicated if they have NULLIFIED or NON_CURRENT status.

Publisher


Issue	Build Number	Description
DE30161	N/A	After publishing the EAEU assembly and recalculating checksums, the index r-022/xml file was generated in the //filesystem/Folder1 location instead of //filesystem/Folder1/Folder2. The checksums were also not updated for the documents added to the assembly. This issue is resolved.
DE29791; [INC0088918]	N/A	When an EAEU submission was published after a leaf was deleted, the attributes CHECKSUMM and CHECK_ALG were included in the <hccd:RegistrationDossierDocDetails> element. This issue is resolved. Now, the CHECKSUMM and CHECK_ALG attributes are not included in the <hccd:RegistrationDossierDocDetails> element. Also, now in the index-r-022.xml file, the CHECKALG attribute is generated as CHECK_ALG.
DE29710; [INC0200183]	N/A	After publishing an assembly, the generated stf.xml files included incorrect links. This issue is resolved.
DE29656; [INC0184736]	N/A	Details of failed jobs were not displayed in the Job Requests query leading to extra effort in troubleshooting. This issue is resolved. Now, detailed information about failed jobs, along with the cause of the failure and document name where applicable, is displayed in the Job Requests.
DE29613; [INC0184045]	N/A	After publishing, xml output included incorrect Applicant ID phone number type. This issue is resolved.
DE29565; [INC0184222]	N/A	When a Japanese submission that included comma-separated values in the assembly was published, the fields Brand Name,Submission Type, Applicant, and Generic Name included in the xml output were incorrect. This issue is resolved. Now, all the fields mentioned above are included in the xml file correctly.
DE29387; [INC0163084, INC0206337]	N/A	After reusing and publishing US study reports content in EU dossier, the order of the tags in the index.xml output location was incorrect. This issue is resolved. Now, tags in the index.xml are generated correctly.
DE29359; [INC0160614]	N/A	After launching Job Requests operation, Job Status data did not correspond to the Job Requests Details, displaying incorrect or outdated information. This issue is resolved. Now, the statuses correspond to the Job Requests Details data, displaying a short summary of errors/warnings detected.
DE29280; [INC0145064]	N/A	Adding the "/" (forward slash) character in assembly metadata resulted in the following issues after publishing. Empty attributes in published output XML for 2.3.P Leaf. Missing galenic-name XML elements in the ch-regional.xml file. Both issues are now resolved. Now, assembly metadata is published correctly even with the "/" (forward slash) character added.
DE29276; [INC0124015]	N/A	Trying to modify the manufacturer with multiline value in the Address attribute resulted in an error. This issue is resolved.
DE29254	N/A	In an assembly with empty leafs, running the Recalculate checksum operation failed. This issue is resolved. Now, the Recalculate checksum operation completes.
DE29174; [INC0143854]	N/A	When importing an assembly with assigned source document from assembly file, the source location path in the Document Attributes window was not populated. This issue is resolved. Now, the source location displays the location path to the assigned source document.
DE28921; [INC0139947, INC0136904]	N/A	After replacing a PDF file in the output location and the recalculating checksum, the wrong checksum was displayed in the XML. This issue is resolved. Now, the correct checksum is displayed in the XML after recalculating the checksum.
DE28912; [INC0139930]	N/A	In two parallel submissions, a replaced leaf was not copied to a working assembly after synchronizing with the submitted view. This resulted in incorrect assembly structure. This issue is resolved. Now, the submitted view synchronization process works correctly and the assembly shows the correct structure.
DE28851; [INC0123232]	N/A	Group Submissions: In an Assembly Plan with multiple applications, when two folders containing leafs and a form were added for each application, the xml file displayed leaf elements under one application entry after publishing. This issue is resolved. Now, the xml file displays leaf elements under each application entry.
DE28846; [INC0127050]	N/A	When publishing STF, the output STF XML file name was being normalized differently than the reference to the STF XML file name in the index.xml file. As a result, the link in the index.xml file to the output STF XML file was broken. Additionally, the normalization method used to create the STF XML file name was determined by the XML definition files assigned to the assembly in Publishing Settings and not the Assembly Type value that is used to determine how to normalize non-STF file names. This sub-minor release now uses the Assembly Type value to determine which normalization method to use for all output file names (including the STF XML file name) as it was in Calyx RIM 6.2. See Assembly Template Attributes.
DE28730	N/A	If assembly contains both target and reference leafs, output location was not populated for a reference leaf if the target leaf was replaced. This issue is resolved. Now, the output location path contains the correct value.
DE28535; [INC0122230]	N/A	Checksums were missing in the XML files in the following cases: JP regional XML: Checksums were missing after the first publish. A subsequent publish displayed the checksum values of the previous publish, not the current one. EU regional XML: Checksums were missing for leafs with a relative output path (For example., ../../ctd-toc.pdf). Reference leafs: Checksum value was that of the target document when it was chosen as the reference leaf target and did not get updated with subsequent publishes. These issues are resolved.
DE28514, DE26746, DE26596; [INC0120502, CS0266424, INC0014091]	N/A	In two parallel submissions, when a leaf was replaced along with the document under it, performing the synchronization process resulted in both the old and current documents displaying under the replaced leaf in the working view. This issue is resolved. Now, only the current document remains after synchronization.
DE28427; [INC0102271]	N/A	API: It was not possible to update a PDS that was already assigned to a new Event. This issue is resolved. Now, a PDS can be updated even if it is already assigned to a new Event.
DE28390; [CS0562479; INC0091145]	N/A	Using the Enter key to separate values in the Concerned Parties field resulted in an extra tag generation that could be deleted only manually. This issue is resolved.

JavaScript must be enabled in order to use this site.Please enable JavaScript in your browser and refresh the page.

Resolved Issues: Calyx RIM 7.2.5

The following issues that were reported to Technical Support have been resolved. Issues are listed in descending order by their tracking numbers. Customer incident numbers that were recorded when the issues were reported are included in brackets [#####] following the tracking number.

If an issue was resolved in a hotfix before the release, the hotfix build number is included in the table.

Registrations


Issue	Build Number	Description
DE30204; [INC0229723]	N/A	Trying to associate 1000+ products to the Registration resulted in the "Invalid reference" error. This issue is resolved. Now, the products are associated successfully.
DE30162; [INC0226907]	N/A	Trying to view a Product Family with 25000+ products in the UI took longer than expected. This issue is resolved.
DE29739	N/A	Using Major Update or Amendment under Wizards > Create Submission for the applications without products resulted in an error. This issue is resolved. Now, these options work correctly for applications without products.
DE29738	N/A	When performing the API Post request, if Write access was set for Product Family/Product Rights, it was not possible to delete a product family without child entities. This issue is resolved. Now, product families can be successfully deleted.
DE29653; [INC0168860]	N/A	In a Registration, when the Full Product Presentation wizard was used to copy its attributes, the package description was duplicated. This issue is resolved.
DE29642	N/A	After entering the search criteria in the Update Applications wizard and clicking Next, the Select Applications page contained two rows for one application with discrepancy in the Region Type and Region values. This issue is resolved. Now, this page contains one row for one application.

Administration


Issue	Build Number	Description
DE28576	N/A	To retrieve results from the queries List of RMS Fields and List of OMS Fields, a DA List Name was required to be selected from the required field Associated DA List Name. This issue is resolved as the Associated DA List Name is no longer required. It is now possible to retrieve RMS and OMS values regardless of Data Administration list association.
DE28186; [TASK0042598]	N/A	After mapping SPOR Terms to Calyx RIM, RMS terms that had NULLIFIED or NON_CURRENT status were replicated. This issue is resolved. Now, RMS terms are not replicated if they have NULLIFIED or NON_CURRENT status.

Publisher


Issue	Build Number	Description
DE30161	N/A	After publishing the EAEU assembly and recalculating checksums, the index r-022/xml file was generated in the //filesystem/Folder1 location instead of //filesystem/Folder1/Folder2. The checksums were also not updated for the documents added to the assembly. This issue is resolved.
DE29791; [INC0088918]	N/A	When an EAEU submission was published after a leaf was deleted, the attributes CHECKSUMM and CHECK_ALG were included in the <hccd:RegistrationDossierDocDetails> element. This issue is resolved. Now, the CHECKSUMM and CHECK_ALG attributes are not included in the <hccd:RegistrationDossierDocDetails> element. Also, now in the index-r-022.xml file, the CHECKALG attribute is generated as CHECK_ALG.
DE29710; [INC0200183]	N/A	After publishing an assembly, the generated stf.xml files included incorrect links. This issue is resolved.
DE29656; [INC0184736]	N/A	Details of failed jobs were not displayed in the Job Requests query leading to extra effort in troubleshooting. This issue is resolved. Now, detailed information about failed jobs, along with the cause of the failure and document name where applicable, is displayed in the Job Requests.
DE29613; [INC0184045]	N/A	After publishing, xml output included incorrect Applicant ID phone number type. This issue is resolved.
DE29565; [INC0184222]	N/A	When a Japanese submission that included comma-separated values in the assembly was published, the fields Brand Name,Submission Type, Applicant, and Generic Name included in the xml output were incorrect. This issue is resolved. Now, all the fields mentioned above are included in the xml file correctly.
DE29387; [INC0163084, INC0206337]	N/A	After reusing and publishing US study reports content in EU dossier, the order of the tags in the index.xml output location was incorrect. This issue is resolved. Now, tags in the index.xml are generated correctly.
DE29359; [INC0160614]	N/A	After launching Job Requests operation, Job Status data did not correspond to the Job Requests Details, displaying incorrect or outdated information. This issue is resolved. Now, the statuses correspond to the Job Requests Details data, displaying a short summary of errors/warnings detected.
DE29280; [INC0145064]	N/A	Adding the "/" (forward slash) character in assembly metadata resulted in the following issues after publishing. Empty attributes in published output XML for 2.3.P Leaf. Missing galenic-name XML elements in the ch-regional.xml file. Both issues are now resolved. Now, assembly metadata is published correctly even with the "/" (forward slash) character added.
DE29276; [INC0124015]	N/A	Trying to modify the manufacturer with multiline value in the Address attribute resulted in an error. This issue is resolved.
DE29254	N/A	In an assembly with empty leafs, running the Recalculate checksum operation failed. This issue is resolved. Now, the Recalculate checksum operation completes.
DE29174; [INC0143854]	N/A	When importing an assembly with assigned source document from assembly file, the source location path in the Document Attributes window was not populated. This issue is resolved. Now, the source location displays the location path to the assigned source document.
DE28921; [INC0139947, INC0136904]	N/A	After replacing a PDF file in the output location and the recalculating checksum, the wrong checksum was displayed in the XML. This issue is resolved. Now, the correct checksum is displayed in the XML after recalculating the checksum.
DE28912; [INC0139930]	N/A	In two parallel submissions, a replaced leaf was not copied to a working assembly after synchronizing with the submitted view. This resulted in incorrect assembly structure. This issue is resolved. Now, the submitted view synchronization process works correctly and the assembly shows the correct structure.
DE28851; [INC0123232]	N/A	Group Submissions: In an Assembly Plan with multiple applications, when two folders containing leafs and a form were added for each application, the xml file displayed leaf elements under one application entry after publishing. This issue is resolved. Now, the xml file displays leaf elements under each application entry.
DE28846; [INC0127050]	N/A	When publishing STF, the output STF XML file name was being normalized differently than the reference to the STF XML file name in the index.xml file. As a result, the link in the index.xml file to the output STF XML file was broken. Additionally, the normalization method used to create the STF XML file name was determined by the XML definition files assigned to the assembly in Publishing Settings and not the Assembly Type value that is used to determine how to normalize non-STF file names. This sub-minor release now uses the Assembly Type value to determine which normalization method to use for all output file names (including the STF XML file name) as it was in Calyx RIM 6.2. See Assembly Template Attributes.
DE28730	N/A	If assembly contains both target and reference leafs, output location was not populated for a reference leaf if the target leaf was replaced. This issue is resolved. Now, the output location path contains the correct value.
DE28535; [INC0122230]	N/A	Checksums were missing in the XML files in the following cases: JP regional XML: Checksums were missing after the first publish. A subsequent publish displayed the checksum values of the previous publish, not the current one. EU regional XML: Checksums were missing for leafs with a relative output path (For example., ../../ctd-toc.pdf). Reference leafs: Checksum value was that of the target document when it was chosen as the reference leaf target and did not get updated with subsequent publishes. These issues are resolved.
DE28514, DE26746, DE26596; [INC0120502, CS0266424, INC0014091]	N/A	In two parallel submissions, when a leaf was replaced along with the document under it, performing the synchronization process resulted in both the old and current documents displaying under the replaced leaf in the working view. This issue is resolved. Now, only the current document remains after synchronization.
DE28427; [INC0102271]	N/A	API: It was not possible to update a PDS that was already assigned to a new Event. This issue is resolved. Now, a PDS can be updated even if it is already assigned to a new Event.
DE28390; [CS0562479; INC0091145]	N/A	Using the Enter key to separate values in the Concerned Parties field resulted in an extra tag generation that could be deleted only manually. This issue is resolved.