Calyx RIM 7.1.5 Release Notes

Calyx RIM 7.1.5 Resolved Issues

Calyx RIM 7.1.5 resolves the following issues.

Common


Issue	Build Number	Description
DE28251; [INC0091561, TASK0042646]	7.1.5.0.0004	Performance issue was experienced when using the Search option on home page for assemblies, sequences and events. This issue is resolved. Search performance issue is now addressed in this release.
DE28120; [INC0094972, INC0092038]	7.1.5.0.0004	The Calyx RIM 7.1.0 migration did not work correctly for product family broad indications. The indication category type ids were not set to Indication. This issue is resolved. Now, the product family broad indications are migrated correctly.
DE27919	7.1.5.0.0004	Reference Active Ingredient under Pharmaceutical Product Active Ingredient was not created when using the API request. This issue is resolved. Reference Active Ingredient is created using API.
DE27750; [INC0086495, INC0084243]	7.1.5.0.0004	The migration did not work correctly for the OMS organization values. The organization data replicated from SPOR duplicating the Location Id. This issue is resolved. Now, the data does not have duplicates.
DE27480; [INC0082793, INC0087569,CS0532792]	7.1.5.0.0004	API query operation failed for the following assembly tree elements. Leaf POST /insight/api/v2/leaf/query Folder POST /insight/api/v2/folder/query Document POST /insight/api/v2/document/query This issue is resolved. Now, the API query returns the status "SUCCESS" with the requested data.

Publishing


Issue	Build Number	Description
DE28266; [INC0104113]	7.1.5.0.0004	After the export/ímport of the assembly file, the DMS Synchronisation was binding the wrong document for a Veeva document when there were two documents in the same folder with the same name. This issue is resolved. Now, the DMS Synchronisation is binding the correct document.
DE28208; [INC0106878, TASK0042719]	7.1.5.0.0004	Incremental publishing removed the `checksum` values for the files that were not published. This issue is resolved. Now, these values are displayed.
DE28204; [INC0095423, INC0108172]	7.1.5.0.0004	The Study Report wizard did not work properly when updating the sub-folders structure for the selected indication. This issue is resolved. Now, the selected indications are updated successfully.
DE28171	7.1.5.0.0004	When the document was assigned from DCTM to a leaf or folder, the time to assign took longer than expected. It happened only for the first time when the document was assigned after the login. This issue is resolved. The performance is improved. Now, the document assignment takes less time.
DE28146; [INC0101586]	7.1.5.0.0004	When an assembly was imported from an XML file, the TOC did not include the Range Start attribute specified before. This issue is resolved. Now, the Range Start attribute is included in the TOC of the imported assembly.
DE27958	7.1.5.0.0004	After publishing a China assembly, Chinese characters were present in the STF file name. For example, stf- 4.2.1.1 主要药效学.xml. This issue is resolved. Now, China characters are automatically renamed as per eCTD normalization rules before exporting output.
DE27915; [INC0092041]	7.1.5.0.0004	Editing a document assigned from DCTM and selecting the previous document version in Bind to Version failed to indicate the presence of a new version in document attributes and assembly tree. This issue is resolved. Now, the new version is indicated in both document attributes and in the assembly tree.
DE27835; [INC0087631]	7.1.5.0.0004	If the element was locked, the color of the locked element did not change when selected. This issue is resolved. The assembly elements such as folder, leaf, and document now appear in the TOC in a different color when selected. This issue is fixed in Submitted, Working, Sequence, and Publishing views.
DE26687; [CS0205991]	7.1.5.0.0004	The PDF Exists value did not change to Yes on the Document Attributes page for the PDF documents assigned from Veeva after the Rendition Identifier was changed to Viewable Rendition. This issue is resolved. Now, the PDF Exists value is displayed as Yes.
DE26679; [CS0191635]	7.1.5.0.0004	When the Apply Binding to all Children option was used to change the rendition identifier, no extraction job was launched for the document and the status PDF exists was not updated to Yes. This issue is resolved. Now, the extraction job is launched for the document and the status PDF exists is updated to Yes.

Registrations


Issue	Build Number	Description
DE28295; [INC0102780]	7.1.5.0.0004	It was not possible to update product family attributes if many values were present in multiple selection list. This issue is resolved. Now, product family attributes are successfully modified.

Rendering


Issue	Build Number	Description
DE27949; [INC0087977]	5.0.3.1.	Paper publishing to the Postscript (PS) file format resulted in the generation of distorted content that was unreadable. This issue is resolved. Now, the paper publishing has the correct file output with comprehensible content.

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

Calyx RIM 7.1.5 Resolved Issues

Calyx RIM 7.1.5 resolves the following issues.

Common


Issue	Build Number	Description
DE28251; [INC0091561, TASK0042646]	7.1.5.0.0004	Performance issue was experienced when using the Search option on home page for assemblies, sequences and events. This issue is resolved. Search performance issue is now addressed in this release.
DE28120; [INC0094972, INC0092038]	7.1.5.0.0004	The Calyx RIM 7.1.0 migration did not work correctly for product family broad indications. The indication category type ids were not set to Indication. This issue is resolved. Now, the product family broad indications are migrated correctly.
DE27919	7.1.5.0.0004	Reference Active Ingredient under Pharmaceutical Product Active Ingredient was not created when using the API request. This issue is resolved. Reference Active Ingredient is created using API.
DE27750; [INC0086495, INC0084243]	7.1.5.0.0004	The migration did not work correctly for the OMS organization values. The organization data replicated from SPOR duplicating the Location Id. This issue is resolved. Now, the data does not have duplicates.
DE27480; [INC0082793, INC0087569,CS0532792]	7.1.5.0.0004	API query operation failed for the following assembly tree elements. Leaf POST /insight/api/v2/leaf/query Folder POST /insight/api/v2/folder/query Document POST /insight/api/v2/document/query This issue is resolved. Now, the API query returns the status "SUCCESS" with the requested data.

Publishing


Issue	Build Number	Description
DE28266; [INC0104113]	7.1.5.0.0004	After the export/ímport of the assembly file, the DMS Synchronisation was binding the wrong document for a Veeva document when there were two documents in the same folder with the same name. This issue is resolved. Now, the DMS Synchronisation is binding the correct document.
DE28208; [INC0106878, TASK0042719]	7.1.5.0.0004	Incremental publishing removed the `checksum` values for the files that were not published. This issue is resolved. Now, these values are displayed.
DE28204; [INC0095423, INC0108172]	7.1.5.0.0004	The Study Report wizard did not work properly when updating the sub-folders structure for the selected indication. This issue is resolved. Now, the selected indications are updated successfully.
DE28171	7.1.5.0.0004	When the document was assigned from DCTM to a leaf or folder, the time to assign took longer than expected. It happened only for the first time when the document was assigned after the login. This issue is resolved. The performance is improved. Now, the document assignment takes less time.
DE28146; [INC0101586]	7.1.5.0.0004	When an assembly was imported from an XML file, the TOC did not include the Range Start attribute specified before. This issue is resolved. Now, the Range Start attribute is included in the TOC of the imported assembly.
DE27958	7.1.5.0.0004	After publishing a China assembly, Chinese characters were present in the STF file name. For example, stf- 4.2.1.1 主要药效学.xml. This issue is resolved. Now, China characters are automatically renamed as per eCTD normalization rules before exporting output.
DE27915; [INC0092041]	7.1.5.0.0004	Editing a document assigned from DCTM and selecting the previous document version in Bind to Version failed to indicate the presence of a new version in document attributes and assembly tree. This issue is resolved. Now, the new version is indicated in both document attributes and in the assembly tree.
DE27835; [INC0087631]	7.1.5.0.0004	If the element was locked, the color of the locked element did not change when selected. This issue is resolved. The assembly elements such as folder, leaf, and document now appear in the TOC in a different color when selected. This issue is fixed in Submitted, Working, Sequence, and Publishing views.
DE26687; [CS0205991]	7.1.5.0.0004	The PDF Exists value did not change to Yes on the Document Attributes page for the PDF documents assigned from Veeva after the Rendition Identifier was changed to Viewable Rendition. This issue is resolved. Now, the PDF Exists value is displayed as Yes.
DE26679; [CS0191635]	7.1.5.0.0004	When the Apply Binding to all Children option was used to change the rendition identifier, no extraction job was launched for the document and the status PDF exists was not updated to Yes. This issue is resolved. Now, the extraction job is launched for the document and the status PDF exists is updated to Yes.

Registrations


Issue	Build Number	Description
DE28295; [INC0102780]	7.1.5.0.0004	It was not possible to update product family attributes if many values were present in multiple selection list. This issue is resolved. Now, product family attributes are successfully modified.

Rendering


Issue	Build Number	Description
DE27949; [INC0087977]	5.0.3.1.	Paper publishing to the Postscript (PS) file format resulted in the generation of distorted content that was unreadable. This issue is resolved. Now, the paper publishing has the correct file output with comprehensible content.