Calyx RIM 6.2 Release Notes

Resolved Issues: Calyx RIM 6.2

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 resolves the following issues.


Issue	Build	Hotfix Build	Description
25738	6.2.0.0.0296	N/A	Some internal Calyx RIM processes may have caused issues that resulted in the `Status 500` error pages appearing in the user interface. However, those issues were recorded as a `SQLException: Protocol violation` message in the server.log file. This issue is resolved by upgrading the Oracle JDBC driver to be fully compatible with the Oracle 12.2.0.1 version.
25726	6.2.0.0.0296	N/A	For MRP (Mutual Recognition Procedure) and DCP (Decentralised Procedure) Application types, the Copy Package Set Registrations wizard did not provide the ability to select the country to copy the Package Set Registration while proceeding with the wizard pages. This issue is resolved. The Copy Package Set Registrations wizard has been updated with a new drop-down list named Country that appears on the following wizard pages for the MRP and DCP Application types: New Package Set specific Registration(s) > Select Package Set(s) page New Product specific Registration(s) > Copy License Code page
25667, 25352, 24982; [00057163, 00053947, 00049818, 00052494]	6.2.0.0.0296	N/A	When you selected an Applicant Contact for the 1 Administrative Information folder in US eCTD Module 1 assembly template (v3.3), the Search and Sort functions did not work in the Select Applicant Contact list. This issue is resolved. The mechanism for data sorting and filtering has been improved. The correct results are now displayed when the Search, Sort, or Filter options are applied.
25622; [00056776]	6.2.0.0.0296	N/A	When you had one Registration with several Product Detail Sets assigned to it, and one assigned Full Product Presentation where Active Ingredient and Substance are identical, after the XEVMPD Submission wizard was completed you received an XML file with one tag for the same Active Ingredient and one tag for the same Substance without duplicating data. However, for the same Indication/Intended Use and Indication value the generated XML file contained duplicate tags. This issue is resolved. One Indication/Intended Use value is present in the generated XML file when the same Indication/Intended Use Detail (non-Veterinary Product Detail Sets), or Indication Detail (Veterinary Product Detail Sets) is associated to several Product Detail Sets that are associated to one Full Product Presentation via Package Sets.
25605 [00056656]	6.2.0.0.0296	N/A	After an event was updated from a workflow, the list of products was not displayed in the Products tab under that Event. This issue is resolved. All associated products are displayed in the Products tab.
25561, 25535 [00056173, 00055825]	6.2.0.0.0296	25561 - 6.1.0.3.0115 25535 - 6.1.0.3.0111	When a multi-select extra field had more than one value and was included in a workflow, not all values were displayed for the field on the Activity page. This issue is resolved. The mechanism of processing the custom multi-select fields is improved to handle fields that contain multiple values.
25557; [00056104]	6.2.0.0.0296	6.1.0.3.0115	When attempting to save changes to a Product Family through a workflow, the error message `Cannot modify active ingredients on a Product Family that has associated Products` was generated. This issue is resolved. The appropriate validation process is improved and the Product Family can now be updated through a workflow.
25554; [00055924]	6.2.0.0.0296	N/A	When creating and associating a PDS using a Product Detail Set template, clicking the Save button more than once resulted in the PDS appearing to be associated with an Event multiple times. This issue is resolved.
25551, 25381; [00056031; 00054223]	6.2.0.0.0296	6.1.0.3.0120	When assigning an Activity or a Task to a user with a User Name containing a comma (,) character, the following appeared: The assigned Activity was not displayed in the My Activities tab invoked from GO TO > Activities or Navigation Pane > Activities. The Task Alert was not displayed in the Alert Center on the Calyx RIM Home Page. The system could not correctly interact with a database because the comma character was not included in the list of allowed special characters that can be processed during the execution of certain operations. This issue is resolved. The system has been updated to add the comma character to the list of allowed special characters that can be processed by the system.
25546; [00055951]	6.2.0.0.0296	6.1.0.3.0117	Due to the Internet Explorer one hour time out, the XEVMPD Audit Report was not returning data and was not responding in an acceptable time limit. This issue is resolved. The Calyx RIM 6.2 release improves performance of the XEVMPD Audit Report functionality.
25542; [00055861]	6.2.0.0.0296	N/A	When modifying a closed event, setting the Event Closed As field to `[Select]` and trying to save changes caused an invalid reference exception to appear and the event itself to become unavailable through any navigation paths. This issue is resolved. A new warning message is displayed stating that Event Closed As is a required field and must be specified prior to saving the changes.
25541; [00055826]	6.2.0.0.0296	6.1.0.3.0111	When completing an activity that required selecting a user field where the distinguished name was greater than 100 characters, the following error message was generated: `"! Exception while executing event-listener"`. This issue is resolved by allowing for distinguished name values up to 255 characters long.
25539; [00055840]	6.2.0.0.0296	N/A	When statuses are deleted from the Event-Country Attributes > Status Dates tab, the system should update both Actual Date and Projected Date attributes to have the `Null` value in the database. However only the `ACTUAL_DATE` (Actual Date) database value was updated correctly and the `SCHED_DATE` (Projected Date) value stayed unchanged. This issue is resolved. When the status is deleted, the `ACTUAL_DATE` and `SCHED_DATE` values are updated to have `Null` value in the event_country_status_schedule database table.
25538, 25495; [00052193, 00058004, 00056979, 00055469]	6.2.0.0.0296	N/A	There were performance issues observed when expanding the Assembly Tree nodes. The performance of expanding the nodes in the assembly tree and refreshing the expanded assembly tree has been improved. For more information on the new version of the assembly tree see Working with New Assembly Tree..
25536; [00055812]	6.2.0.0.0296	6.1.0.3.0116	A deadlock occurred in Calyx RIM when several workflow actions were performed when a long-running transaction (for example, lifecycle event) was in progress. When the workflow Activiti engine inserts a new row in a table in the Activiti schema, it uses an internal `DbIdGenerator` to generate the next ID value. The `DbIdGenerator` has a setting for `idBlockSize` that determines how many IDs to distribute before going back to the database for the next block. When a long-running transaction requested a new ID block, and then another transaction requested a new ID block before the first long-running transaction was committed, a deadlock occurred. This release reduces the possibility of a deadlock by increasing the default block size from 2,500 to 50,000. Also, this release enables the default block size value to be configurable by adding the following setting in the insight.var file specifying the appropriate block size: `activiti.blockSize=50000` Note: 50000 is a default size.
25526; [00055788]	6.2.0.0.0296	N/A	The `Yes` value set in the Publishing Settings Library > Default Values for the Use Native File attribute was not inherited by the leaf elements created automatically by associating documents with the folders. This issue is resolved. When the leaf is automatically created, the value set for the Use Native File attribute in the Publishing Settings Library is preserved.
25516; [00055405]	6.2.0.0.0296	6.1.0.3.0117	Updating the Publishing Settings to add or remove a DTD sometimes took much longer in Calyx RIM 6.2 compared to previous versions. This release improves the performance by causing Oracle to choose a better execution plan when updating Publishing Settings to add or remove a DTD.
25511; [00055024]	6.2.0.0.0296	N/A	In the Global Project Plan wizard, the manufacturers available for selection in the Manufacturer drop-down list were displayed in a random order for the following Update Product Detail Set Project > Add Manufacturer flows: Add Active Ingredient Manufacturer Add Active Ingredient Manufacturing Process Function Manufacturer Add Substance Manufacturer Add PDS Function Manufacturer This issue is resolved. The sorting mechanism has been added to display the Manufacturer values in the Manufacturer drop-down list in alphabetical order.
25510; [00055531, 00057192]	6.2.0.0.0296	N/A	For the following listed queries, the Substance Selection list (Search Criteria > Active Ingredient Name > Select) displayed all Active Ingredients from the Data Administration > Product Family Maintenance > Substance Values table: Product Detail Management > List of Active Ingredient Manufacturers Product Detail Management > List of Active Ingredient Function Manufacturers Product Detail Management > List of Active Ingredient Material Manufacturers Product Detail Management > List of Registrations with Active Ingredients Registration Planning and Tracking > List of Product Families In Calyx RIM 6.2, the Substance Selection list was reworked to display only Active Ingredients associated to the product families selected in the Product Family/Product Family Name multi-select list.
25508; [00055608]	6.2.0.0.0296	6.1.0.3.0111	In Calyx RIM for Analytics, the XEVMPD Audit Report returned duplicated results when a product was associated with more than one application. This issue is resolved.
25501, 25464; [00054523, 00054500, 00055108, 00054523]	6.2.0.0.0296	N/A	Performance issues were observed when the Ready for Submission wizard retargeted Reference Leafs for the entire Working View after the Assembly Plan was merged. This could cause the job to fail and the `Source leaf cannot be a reference leaf` error message to appear in the Job Details. The performance issue is resolved. The retargeting reference leafs system function is improved. The job is successfully completed and no error messages are displayed in the Job Details when the Ready for Submission wizard is finished.
25484; [00055433]	6.2.0.0.0296	6.1.0.3.0115	Volumes were created with blank names if the Assembly was volumized out of order. This issue is resolved. The mechanism of identifying the sibling volumes during the Bulk Volumization by Sheets operation has been improved.
25483; [00055072]	6.2.0.0.0296	6.1.0.3.0100	When in the Working View with Try New Version of an assembly tree option selected, using drag and drop to replace a document in a leaf with NEW status resulted in the leaf status not being automatically updated to REPLACE. This issue is resolved. The assign DMS nodes function is improved to refresh the assembly tree when the assign action is completed.
25481; [00055174]	6.2.0.0.0296	N/A	When requesting a DMS Synchronization from the Publishing View, all nodes from previous sequences were processed and that could take an extended period of time to complete. This issue is resolved. The performance of DMS Synchronization invoked from the Publishing View has been improved.
25475; [00054686]	6.2.0.0.0296	6.1.0.4.0041	Attempting to generate a volume TOC resulted in a `Failed to resolve TocEntry Name` error in the Job Requests window. The error `ORA-01438: value larger than specified precision allowed for this column` was also seen in the server.log.file. This issue is resolved. The precision constraint in the `ods.toc_entry.absolute_seq_no` column has been removed.
25469	6.2.0.0.0296		Attempting to delete a Dose Schedule PDS Detail resulted in an error. This issue is resolved.
25465	6.2.0.0.0296	6.1.0.3.0100	In Calyx RIM 6.1, an update trigger on the content table was modified to not create entries if the update was due to a renumbering event. The trigger, however, denoted updates to the content table as inserts instead of updates. The database script included with this release corrects the trigger and repairs affected data.
25461; [00055117]	6.2.0.0.0296	N/A	For the Canadian eCTD Module 1 v2.2, entering invalid numeric-only value for the Sequence Description field caused an `UndeclaredThrowableException` error message to appear in the publish Job Details. This issue is resolved. The revised message explains that numeric-only values are not supported for the Sequence Description field, and is displayed when you try to save the metadata.
25460; [00055109]	6.2.0.0.0296	N/A	When creating a New (Empty) Standalone Assembly, or a Standalone Assembly from an Assembly File using the New > Standalone Assembly option, the following fields were displayed as non-required: Publishing Settings Library Use Source Assembly Publishing Settings Library Saving those Standalone Assemblies without making any selections in the listed fields caused warning messages to appear. This issue is resolved. The fields are followed by an asterisk (*) indicating that they are required.
25457; [00055111, 00054917]	6.2.0.0.0296	N/A	In the unlocked Submitted View of an assembly you were unable to remove empty folders using the Delete icon on the Folder Attributes, if the Try New Version of an assembly tree option was selected. This issue is resolved. Now you can delete empty folders in the new version of an assembly tree.
25440; [00055119]	6.2.0.0.0296	6.1.0.4.0041	When creating a Working Assembly using the Create eCTD wizard, the error `ORA-00932: inconsistent datatypes: expected NUMBER got BINARY` occurred if the checkbox Update the sub-folder structure for was selected. This issue is resolved. The Create eCTD wizard can be finished successfully without displaying any errors.
25434; [00054636]	6.2.0.0.0296	N/A	When you selected the Create Missing Renditions and Extractions option for a PDF document with PDF Exists value set to `Yes` and Extractions Exist value set to `No`, the job was completed. However, the following message was displayed in the Job Requests details page: `No document to render`. This issue is resolved. An additional verification has been added for the Prepare to Publish. The system checks the Extractions Exist flag of a source document and the functionality now works as designed.
25422	6.2.0.0.0296	N/A	The following columns that display data related to Substance PDS Detail child entities were missing from the Product Detail Management > Application History and Product Detail Management > Application QC Status History queries: Application History Query: Substance Manufacturing Process Details Changed? Substance Manufacturing Process Function Details Changed? Substance Manufacturing Process Function Manufacturer Details Changed? Substance Manufacturing Process Step Details Changed? Substance Manufacturing Process Step Function Details Changed? Substance Manufacturing Process Step Function Manufacturer Details Changed? Substance Material Details Changed? Substance Material Manufacturer Details Changed? Application QC Status History Report: Substance Manufacturing Process Details QC Passed? Substance Manufacturing Process Function Details QC Passed? Substance Manufacturing Process Function Manufacturer Details QC Passed? Substance Manufacturing Process Step Details QC Passed? Substance Manufacturing Process Step Function Details QC Passed? Substance Manufacturing Process Step Function Manufacturer Details QC Passed? Substance Material Details QC Passed? Substance Material Manufacturer Details QC Passed? This issue is resolved. The appropriate values are now available for selection in the Display Columns multi-select field on the Application History Query > Enter Search Criteria and Application QC Status History Report > Enter Search Criteria pages. The appropriate columns appear on the Search Results page of both queries for the Substance PDS Detail related entities, when those columns are selected. The value presented in each of the columns is a hyperlink to the specific subreport.
25414; [00054605]	6.2.0.0.0296	6.1.0.4.0041	The `FLASHBACK_TIME=SYSTIMESTAMP` parameter was added to the `expdp` commands in the `dpexportinsight.sql` to keep all exported tables synchronised to the same point of time.
25410; [00055170, 00054235]	6.2.0.0.0296	6.1.0.3.0099	For US grouped submissions, the order of M1 metadata unintentionally affected whether or not the primary application was listed first in the published us-regional.xml. This issue is resolved. The primary application is always listed first in the `regional.xml`.
25405; [00054019]	6.2.0.0.0296	6.1.0.3.0093	For US eCTD v2.01 submissions: When using the Import eCTD to Application wizard (Import from eCTD icon on the Application attributes page) to import several sequences having 1.14.1.X subfolders introduced non-sequentially in different sequences, the nodes were not ordered numerically in the submitted view created by the import process. This issue is resolved.
25401; [00053089]	6.2.0.0.0296	6.1.0.3.0100	When the Rendition Identifier for an assembly document without a custom rendition was set to a non-standard value and the Use Standard Rendition option was selected for Missing Rendition Identifier Handling in Publishing Settings, Linking plug-in (PDF) was allowing you to create links in the standard rendition of the document instead of displaying an error as expected. This issue is resolved.
25395; [00054382]	6.2.0.0.0296	6.1.0.3.0092	When Calyx RIM attempted to create a DataExchangeExport file with the exact same timestamp-inclusive file name as an already existing export file, the duplicate name file would not be created. This issue is resolved by adding milliseconds to the timestamp portion of the filename to avoid duplicates.
25391; [00054454, 00054327, 00053609]	6.2.0.0.0296	`DB_hotfix6_1_0_chf3_0136.zip`	`ORA-01789` and `ORA-00942` errors occurred during the Calyx RIM6.2 CHF 3 migration when the AUD table had an obsolete column that did not exist in the corresponding table in the ODS/MGR/SEC schema. This issue is resolved and is no longer presented when migrating to Calyx RIM 6.2 from the previous Calyx RIM versions. Also, the `RULE` hint is added to improve the migration performance.
25379; [00054093]	6.2.0.0.0296	6.1.0.3.0092	When a Document with a Rendition Identifier that had been assigned to a document by default was later updated in the Working View of the Assembly to have any other Rendition Identifier value from Data Administration > DMS Integration > Rendition Identifier Values table, the change was not displayed in the Publishing View of the Assembly. However, in the published output the rendition was set correctly. This issue is resolved. During the document create or update actions, the list of specific attributes are copied from the Working View of an Assembly to the Publishing View. To have the Rendition Identifier value in the list that is copied to the Publishing View of an Assembly, the missing RenditionModifierTypeId value has been added to the system Copy function.
25376; [00054015, 00053356]	6.2.0.0.0296	N/A	Performance issues were observed when the system processed leafs in a sequence assembly within one application, for example converting a standard leaf to be a reference leaf. To fix the performance issue, the query has been optimized.
25370; [00053016]	6.2.0.0.0296	6.1.0.3.0100	When the jp-regional-index.xml file was replaced in Sequence 0001 and again in Sequence 0002, the index.xml file for Sequence 0002 referenced the 0000 regional xml file as the modified file instead of the 0001 version. This issue is resolved. For Japanese submissions, the method of searching for the sequence with the latest updated content is improved.
25361; [00054034]	6.2.0.0.0296	6.0.0.6.0027	If a Product Detail Set (PDS) had multiple approved Package Set details with approved Packaging details, the Product Detail Management > List of Registrations with Packaging query displayed each package set on the Search Results page, however only one Package Set was assigned to the Registration. This issue is resolved. The query Search Results page now displays only Package Set details associated to the Registration.
25358; [00053900]	6.2.0.0.0296	N/A	The Applicant Contact table for the US Module 1 eCTD v2.3 specification (DTD v3.3) Assembly > 1 Administrative Information folder displayed the Telephone and Email values as dimmed and unavailable, if: There were several Contact Telephone Number values with different telephone number types, but identical telephone numbers, assigned and one of them had been deactivated later on the Data Administration > Submission Maintenance > Applicant Contact Values > Applicant Contact Telephone Number tab. There were several Contact Email values assigned and one of them had been deactivated later on the Data Administration > Submission Maintenance > Applicant Contact Values > Applicant Contact Email tab. The issue is resolved: For Contact Email, only the deactivated value is displayed as dimmed and unavailable. For the Contact Telephone Number, the system checks the unique combination of the Telephone Number Type and Telephone Number values and indicates only the deactivated value to be displayed as dimmed and unavailable.
25348; [00054367]	6.2.0.0.0296	6.1.0.3.0117	In Calyx RIM 6.2, the queries related to the following areas have been optimized to reduce the possibility of database locks: Getting Events under Application Actions with the XEVMPD change history DTD change for an Assembly As part of this optimization, a new index has been added to the XEVMPD change history.
25345; [00053849]	6.2.0.0.0296	DB_hotfix6_1_0_chf3_0137.zip	The performance of the upgrade script that was used to migrate to Calyx RIM 6.1 CHF 3 has been improved. The DB_hotfix6_1_0_chf3_0137.zip upgrade script supercedes the DB_hotfix6_1_0_chf3_0136.zip upgrade script and must be used to migrate to Calyx RIM 6.1 CHF 3.
25333	6.2.0.0.0296	N/A	When setting up a notification for Registration FPP Attachment and selecting the When a value changes option to display the notification in the Alert Center, the notification was triggered. However, the entity URL on the Notification Attributes page displayed incorrectly concatenated data: Internal Name, Country, Attachment Name, and Attachment Version. This issue is resolved. The URL is displayed as a concatenation of Internal Name, Language, Attachment Name, and Attachment Version.
25324	6.2.0.0.0296	N/A	It was not possible to re-target a link that was already targeted to a bookmark. This issue is resolved.
25322	6.2.0.0.0296	N/A	When creating a new assembly using either the Existing Template, Assembly, or View option, the OK button on the Search Assembly Wizard remained unavailable after selecting the matching assembly. This issue is resolved. The OK button becomes active after you select the matching assembly and then click on Next.
25312; [00058254]	6.2.0.0.0296	6.1.0.4.0047	Attempting to delete a link from the Link Inspector results failed with an error. This issue is resolved. No error message is displayed when you delete a link from the Link Inspector results.
25309; [00054064; 00053322]	6.2.0.0.0296	6.1.0.3.0092	Calyx RIM 6.2 introduces a fix for Calyx RIM for Analytics to decrease the amount of time needed to load the Manufacturer Report page with the selection criteria. To improve the report performance, the PDS Name filter criterion has been removed from the Manufacturer Report filter criteria selection page. The PDS Name column on the report Search Results page is preserved.
25308; [00053352]	6.2.0.0.0296	N/A	In the Calyx RIM 6.1 CHF 1 and Calyx RIM 6.1 CHF 2 upgrade scripts, passwords from the `define.migration` file were stored and displayed in the resulting `master.sql` log file. The Calyx RIM 6.2 upgrade script resolves this issue.
25299; [00053287]	6.2.0.0.0296	6.1.0.3.0093	When assigning Withdrawal Time Unit values to the Species > Route of Administration > Withdrawal Times PDS Detail during the creation of a PDS Template, the Withdrawal Time Unit drop-down list displayed values that had been deactivated in Data Administration. This issue is resolved. The system has been enhanced to add a filtering option to the Species > Route of Administration > Withdrawal Times > Withdrawal Time Unit field that excludes the inactive values from the list.
25272; [00052896]	6.2.0.0.0296	N/A	After applying the upgrade script, importing the assembly template into Calyx RIM for the first time caused the following error message to be displayed: `The object you are acting on has been deleted or modified by another user. Refresh your object to view the current information.` This issue is resolved.
25268; [00052092]	6.2.0.0.0296	6.1.0.3.0089	Running the Update Status wizard from a Product Family Attributes page resulted in the unintentional changing of the Reviewing Country value for an application, when there was more than one country assigned. This issue is resolved. The reviewing country stays unchanged after the Update Status wizard is finished.
25266; [00052934]	6.2.0.0.0296	6.1.0.3.0089	Using the eCTD Import wizard to import an assembly that had a node-extension folder with hundreds of child leaf nodes took many hours to complete. This issue is resolved by separating one large import transaction into multiple smaller import transactions.
25264; [00052928]	6.2.0.0.0296	N/A	The M1 folder disappeared completely from the Assembly Tree during expand attempt if there were any nodes that contained a hyphen (‐) in the node name. This issue is resolved. This symbol is ignored in the New Assembly Tree. In addition, a specific script replace_soft-hyphen_with_minus.zip that is aimed to replace each instance of the hyphen across the Assembly Tree has been introduced. Please contact Technical Support for more information.
25246 [00052728]	6.2.0.0.0296	6.1.0.3.0092	Values in drop-down lists on the following Add PDS Detail pages were being sorted in a case-sensitive manner. Add Active Ingredient > Active Ingredient drop-down list Add Function > Function drop-down list Add Manufacturer > Manufacturer drop-down list This issue is resolved. The case of values is ignored during the sorting process.
25245; [00052399]	6.2.0.0.0296	N/A	Using the Update Status wizard for an Event with an associated Sequence caused an extra APPROVED Sequence status to appear in the Status Dates tab, when the Event was closed as WITHDRAWN or NOT APPROVED. This issue is resolved. The correct statuses are now displayed in the Sequence > Status Dates tab, when the Update Status wizard is passed.
25221; [00052338]	6.2.0.0.0296	6.1.0.3.0093	Running the Bulk Update Events wizard (launched from the Project Attributes page) when nothing was selected in the non-required Secondary Event Type field resulted in the Secondary Event Type values being cleared unintentionally for all applicable events. This issue is resolved. The Secondary Event Type values are preserved when the wizard is finished if this field has not been selected for modifications on the Select Attributes to update page of the wizard.
25215; [00052305]	6.2.0.0.0296	N/A	There was a performance issue in displaying a large quantity of users in Calyx RIM Security Administration. This issue is resolved: `ISM.DV_USER` view has been updated `ISM.R_SEC` package has been updated `lv_rc` line has been increased from VARCHAR2(4000) to VARCHAR2(32767)
25210; [00052191]	6.2.0.0.0296	N/A	There was a performance issue when logging on to Calyx RIM for Analytics. This issue is resolved. The following has been updated: An index `X2USR` has been added to the USR table, NAME field The `ISM.DV_USER_ACCESS_LEVEL` view has been updated
25209; [00053438, 00052279, 00052147, 00052137]	6.2.0.0.0296	hotfix6_1_0_chf1_0115.zip	The following error occurred during the Calyx RIM 6.1 CHF 1 migration: `ORA-01555: snapshot too old` This issue is resolved in the DB_hotfix6_1_0_chf4_0024.zip migration script that is used to migrate to Calyx RIM 6.1 CHF 4 from the previous Calyx RIM 6.1 CHFs. After performing the migration to Calyx RIM 6.1 CHF 4 and proceeding with the migration to Calyx RIM 6.2 using the appropriate migration script, no migration errors appear.
25206; [00051373, 00052844]	6.2.0.0.0296	N/A	If an assembly had been created from the existing Submitted View with the Retarget Copied Reference Leaf option selected, the following issues occurred: The Find Reference Leaf Elements option invoked on the Leaf element of the created assembly displayed the reference leaf elements of the copied submitted view. The created assembly could not be deleted. These issues are resolved: The Find Reference Leaf Elements option now displays the reference leaf elements of the current assembly. The created assembly can be deleted.
25197; [00052103]	6.2.0.0.0296	master.zip hotfix6_1_0_chf1_0115.zip	Data copied from a field in the `MGR.Application.Term_Withdraw_Reason` table to a field in the new `MGR.Term_with_reason_type` table that was too small resulted in the following errors: `ORA12899: value too large for column` `ORA-00001: unique constraint` This issue is resolved in the DB_hotfix6_1_0_chf4_0024.zip migration script that is used to migrate to Calyx RIM 6.1 CHF 4 from the previous Calyx RIM 6.1 CHFs. After performing the migration to Calyx RIM 6.1 CHF 4 and proceeding with the migration to Calyx RIM 6.2 using the appropriate migration script, no migration errors appear.
25182; [00051882]	6.2.0.0.0296	N/A	The Apache Commons Collections library was vulnerable to insecure deserialisation of data, which could result in arbitrary code execution. To fix this issue, the Apache Commons Collections version 3.2.2 has been applied to the Calyx RIM 6.2 Application Server. The Apache Commons Collections library version 3.2.2 mitigates the vulnerability by disabling the insecure functionality.
25158; [00051744]	6.2.0.0.0296	InsightForAnalytics.zip 6.1.0.3.0013 (InsightForAnalyics-6.1-chf3-hf1.zip ) WFConfig.zip 6.1.0.3.0009 (WFConfig-6.1-chf3-hf1.zip)	The log on to the Calyx RIM for Analytics failed if the Display Name contained the ampersand (&) character. This issue is resolved by escaping the ampersand characters for Display Name value in the wfsqlusers.fex and user_name.fex files.
25156	6.2.0.0.0296	6.1.0.2.0017	The error `ORA-02292: integrity constraint (ODS.R_789) violated - child record found` occurred when attempting to delete an application having a lifecycled assembly with a reference leaf. This issue is resolved.
25141; [00051550]	6.2.0.0.0296	6.1.0.3.0099	Attempting to import a Japanese submission having a `DELETE` operation in module 1 failed. This issue is resolved by updating the `xlink:href` attribute processing for the Leaf that has a `DELETE` status.
25140; [00051261]	6.2.0.0.0296	N/A	It was possible to delete a sequence with a working assembly that was created by another user, or in another tab. The Delete button on the Sequence Attributes page was enabled until the page was refreshed. This issue is resolved by adding an additional check to identify the presence of working assembly in the verifiable sequence. If the working assembly exists, the warning message is displayed.
25134; [00052137, 00051492, 00051212]	6.2.0.0.0296	hotfix6_1_0_chf1_0115.zip	During the migration from Calyx RIM 5.1 to Calyx RIM 6.1 CHF 1 the issue of an empty GUID column for leafs and folders was observed. This issue resulted in the following errors: `Error adding new not null constraint on FOLDER.GUID` `ORA-02296: cannot enable (ODS.) - null values found` `Error adding new not null constraint on LEAF.GUID` `ORA-02296: cannot enable (ODS.) - null values found` This issue is resolved in the DB_hotfix6_1_0_chf4_0024.zip migration script that is used to migrate to Calyx RIM 6.1 CHF 4 from the previous Calyx RIM 6.1 CHFs. After performing the migration to Calyx RIM 6.1 CHF 4 and proceeding with the migration to Calyx RIM 6.2 using the appropriate migration script, no migration errors appear.
25110, 25001; [00048772, 00049481, 00049976 , 00050201, 00050749, 00051273, 00051803]	6.2.0.0.0296	25110 - 6.0.0.5.0004, 6.1.0.2.0017 25001 - 6.0.0.5.0004, 6.1.0.2.0017	In Calyx RIM 6.1, if the default styles were not overridden, all native links were processed with the style obtained from the default link settings profile. This resulted in performance degradation of the publishing process. This issue is resolved with Calyx RIM 6.2, the functionality is modified by not altering native links unless the target page of the link is no longer in the same file due to a the file being split, or if the profile is not the default profile.
25091; [00049218]	6.2.0.0.0296	N/A	When Prepare to Publish, or Publish, was executed for a submission with any assigned documents that contained Xref links, you could experience an `UndeclaredThrowableException` error. This error was caused by Xrefs that are no longer supported by Calyx RIM. This issue is resolved: Xrefs are ignored and the link annotations are not created in the PDF rendition. All CDCXrefs in an in-process rendition, or PDF document, or rendition to be published, are always deleted. CDCXrefs no longer cause the publish request to fail.
25085; [00051005]	6.2.0.0.0296	N/A	When you created the Publishing Settings Library Template using the New > Publishing Settings Library Template option, one of the following issues occurred: Clicking Save after the session timeout, displayed the warning message: `You have already sent this request to the server. Please try again.` Clicking Save for the second time saved the entity. Navigating to the New > Publishing Settings Library Template option after the session timeout opened the Create Publishing Settings Library page, with the Publishing Library Owner field set to guest. Filling the attributes and clicking Save saved the entity. This issue is resolved. The system now does not allow you to save the Publishing Settings Library Template after the session timeout.
25075; [00050986]	6.2.0.0.0296	N/A	Navigating to Calyx RIM for Analytics while logged on to the Calyx RIM system caused the wrong user name value to be sent to the Calyx RIM for Analytics server. This issue is resolved. The system now uses the correct user name value for the SSO (Single Sign On) to the Calyx RIM for Analytics system.
25070; [00052810, 00051949, 00051259, 00050874]	6.2.0.0.0296	6.1.0.3.0093	When a user session expired, a guest account with no privileges was assigned to the session. Any subsequent action resulted in the login page being displayed. However, if the user was still idle when the guest session expired, errors were generated and logged in the `server.log` file. This issue is resolved. Calyx RIM no longer attempts to save settings for the guest user when the guest user session expires.
25058; [00050726]	6.2.0.0.0296	6.1.0.2.0015	Inactive functions were available for selection when executing the Add Active Ingredient Manufacturing Process Function Manufacturer step in the Global Project Plan Wizard > Update a Product Detail Set Project flow. This issue is resolved. Only Active functions are available for selection.
25054; [00050668]	6.2.0.0.0296	N/A	In email notifications, the old application logo was displayed and the Calyx RIM Manager notification system was indicated as the sender. This issue is resolved. The sender name is updated and is displayed as Calyx RIM notification system. The application logo is replaced with the most current one.
25045; [00050172, 00052819]	6.2.0.0.0296	N/A	The system allowed you to disassociate the approved Product Detail Set (PDS) with a withdrawn Shelf Life/Storage Condition detail from the Event, but the `ORA-02292: integrity constraint (MGR.R_732B) violated - child record found` error occurred. This issue is resolved. The system now does not allow the disassociation if there are data dependencies.
25014; [00050210]	6.2.0.0.0296	N/A	For sequence assemblies only, you could convert a leaf to be a reference leaf referencing itself, which violated the business rule that a leaf cannot reference itself. This issue is resolved. Now, if a user attempts to create a leaf referencing itself, the following error message is displayed: `A leaf cannot reference itself.`
25013; [00050091]	6.2.0.0.0296	N/A	When using the Recalculate Checksums option, the backbone files in the electronic output location were not updated if the electronic output location contained a normalized Application Code. Instead, new backbone files were published to the location which was 2 folders above the correct one, in case if during the normalization process the Application Code value was changed. This issue is resolved.
25002; [00050016]	6.2.0.0.0296	N/A	When creating a new assembly using Creating Assembly from a Template, Assembly, or View option or Import Assembly Wizard, data under the Sequence Assemblies tab was not appearing in a reasonable amount of time. This issue is resolved.
24959; [0004923, 00050581, 00051103]	6.2.0.0.0296	6.0.0.5.0008 6.1.0.2.0017	Long publishing time issues could occur due to Oracle choosing an inefficient execution plan for a particular query. This issue is resolved. The problematic query is rewritten to prohibit Oracle from choosing the inefficient execution plan.
24958; [00049474]	6.2.0.0.0296	N/A	When you opened the Assembly tab, a "Loading" message appeared but the operation was not completed in a reasonable amount of time for the Assembly Attributes page. However, the assembly tree and assembly tree elements were fully loaded and accessible. This issue is resolved.
24956; [00049263]	6.2.0.0.0296	N/A	When the Bulk Update Events wizard was invoked from the Project Attributes page, you could update the events with countries to which you had Read access. This issue is resolved. The Select Events to Update page now lists only events with countries, to which your access is set to at least Write.
24923; [00049174, 00049530]	6.2.0.0.0296	N/A	The 1.A.5 Comparison Table section in Thailand Module 1 Specification v1.0 had incorrect leaf output file name comparison.pdf. This issue is resolved. The leaf output file name is now appearing as comparison-table.pdf.
24896; [00048871, 00049238, 00024896, 00050205]	6.2.0.0.0296	N/A	When trying to extract a document with a bookmark that contained a non-Unicode character, the extract job was displayed as Completed. However, the Job Details contained an error with an exception, and the Assembly > Document Attributes had the Extract Exists field set to No. The issue with the job statuses is resolved. The correct status, Failed, is now displayed when a document is not extracted.
24891; [00047906]	6.2.0.0.0296	6.0.0.3.0037	Leafs and documents with names beginning with stf- were omitted during the eCTD Import process because the code interpreted all files located in study folders beginning with stf- as STF XML files. This issue is resolved.
24876; [00048681]	6.2.0.0.0296	6.0.0.3.0037	Attempting to remove a sequence from a lifecycle was not completing in a reasonable amount of time even after increasing the timeout value. The delay occurred due to the unnecessary calls to two queries. This issue is resolved.
24860; [00048499, 00054314]	6.2.0.0.0296	N/A	When using the eCTD Import process to import an assembly containing reference leafs that target leafs further down in the assembly tree, the reference leafs and target leafs were switched in the imported assembly. This issue is resolved for the region specific Module 1, and also Module 2, Module 3, Module 4, and Module 5 that are common for all regions.
24832; [00047932]	6.2.0.0.0296	5.1.0.5.0013 6.0.0.3.0034	Using the Import Assembly Wizard to import an assembly with the option to retarget selected reference leafs sometimes resulted in an invalid reference error. This issue is resolved.
24800; [00047397]	6.2.0.0.0296	6.1.0.3.0092	For null values on sequence `ACTUAL_DATE` fields from `01-JAN-1901` to `01-JAN-1900` the default date is set to avoid issues with incorrect event statuses appearing after migrations that set the values to dates between those two values.
24704	6.2.0.0.0296	N/A	The issue of incorrect display names for the Full Product Presentation and Registration FPP Attachment comment fields has been resolved: The Full Product Presentation Comments field has been reworked to be a display-only field on the View Full Product Presentation Attributes page. The Full Product Presentation Add Comment field has been added to the Create/Modify Full Product Presentation Attributes pages. The Attachment Comments field has been renamed to be Registration FPP Attachment Comments. See Fields Added: Calyx RIM 6.2 and Fields Updated: Calyx RIM 6.2.
24703	6.2.0.0.0296	N/A	The discussion thread related fields had the incorrect display names for the Product, Pharmaceutical Product, Event, Registration, and Sequence entities. This issue is resolved. To support the naming convention across the Calyx RIM system, the display names had been reworked to be: Product > Product Add Comment Pharmaceutical Product > Pharmaceutical Product Add Comment Event > Event Add Comment Registration > Registration Add Comment Sequence > Sequence Add Comment See Fields Updated: Calyx RIM 6.2.
24641	6.2.0.0.0296		When trying to delete a Product Details Set (PDS) with the child details added under the Substance node, the Delete button appeared dimmed after those details with Approved or Not Approved status had been deleted. This meant that the PDS could not be deleted due to data dependencies. This issue is resolved. The Delete button is now available and the PDS can be deleted.
24561	6.2.0.0.0296	N/A	The Next Renewal Date column on the Registrations tab was displayed incorrectly as First Renewal Date when you were navigating to it from the Product Family Attributes and Product Attributes pages. This issue is resolved. The column name is now displayed correctly for Product Family Attributes, Product Attributes, and Application Attributes pages.
24474; [00044014]	6.2.0.0.0296	N/A	A client reported a performance issue that appeared when changing the status to APPROVED for Event entities that were created as part of a migration. This issue has been resolved and is no longer reproducible on the latest Calyx RIM versions.
24422	6.2.0.0.0296	N/A	When using the Veeva DMS, an error occurred while attempting to bind a document to any label other than CURRENT. This issue is resolved. When the selected label is other than CURRENT, a warning message informs you that the document must be bound to a CURRENT label only.
24408; [00032393]	6.2.0.0.0296	N/A	The sorting for Manufacturer Details in the PDS tree was performed by the Manufacturer Status Date attribute. This issue is resolved. The Manufacturer Details are now sorted alphabetically.
22781; [00029737, 00044188]	6.2.0.0.0296	N/A	You were not able to modify the Active Ingredients field on the Modify Product Family page after the associated Product, that contained a Component, was deleted. This issue is resolved. Once the related Product along with its Component is deleted, the Active Ingredients field is displayed as a selection list and is available for modifications on the Modify Product Family page.
23690; [00051715, 00048203, 00047314]	6.2.0.0.0296	6.1.0.3.0084	Closing an event as Approved did not set the Application Status to Approved if the current Application Status value was Submitted. This issue is resolved.
22697; [00027525]	6.2.0.0.0296	N/A	When an Event was closed with a status of Withdrawn, all related Sequence Status Dates were changed to the withdrawn date. This issue is resolved. When an event is now closed, the Sequence will keep its status as well as the date for any sequence with a status of Approved, Not Approved, Submitted, or Withdrawn. If the Sequence status is Planned, it will be changed to Withdrawn.
22028; [198009FW]	6.2.0.0.0296	N/A	When changing the value in Product Family Type multiple selection field, refreshing of the List of Product Families page took several minutes. This issue occurred on all multiple selection fields across the system. This issue is resolved for Internet Explorer 11 and Google Chrome browsers.
20703; [144950FW, 00043370]	6.2.0.0.0296	N/A	You were not able to select multiple documents using the Shift and Ctrl keys and drag them within the assembly. This issue is resolved with the New Version of the Assembly Tree introduced in Calyx RIM 6.2.
18655	6.2.0.0.0296	N/A	Create eCTD wizard failed if many sets of metadata were applied. This issue has been resolved and is no longer reproducible on the latest Calyx RIM versions.

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

Resolved Issues: Calyx RIM 6.2

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 resolves the following issues.


Issue	Build	Hotfix Build	Description
25738	6.2.0.0.0296	N/A	Some internal Calyx RIM processes may have caused issues that resulted in the `Status 500` error pages appearing in the user interface. However, those issues were recorded as a `SQLException: Protocol violation` message in the server.log file. This issue is resolved by upgrading the Oracle JDBC driver to be fully compatible with the Oracle 12.2.0.1 version.
25726	6.2.0.0.0296	N/A	For MRP (Mutual Recognition Procedure) and DCP (Decentralised Procedure) Application types, the Copy Package Set Registrations wizard did not provide the ability to select the country to copy the Package Set Registration while proceeding with the wizard pages. This issue is resolved. The Copy Package Set Registrations wizard has been updated with a new drop-down list named Country that appears on the following wizard pages for the MRP and DCP Application types: New Package Set specific Registration(s) > Select Package Set(s) page New Product specific Registration(s) > Copy License Code page
25667, 25352, 24982; [00057163, 00053947, 00049818, 00052494]	6.2.0.0.0296	N/A	When you selected an Applicant Contact for the 1 Administrative Information folder in US eCTD Module 1 assembly template (v3.3), the Search and Sort functions did not work in the Select Applicant Contact list. This issue is resolved. The mechanism for data sorting and filtering has been improved. The correct results are now displayed when the Search, Sort, or Filter options are applied.
25622; [00056776]	6.2.0.0.0296	N/A	When you had one Registration with several Product Detail Sets assigned to it, and one assigned Full Product Presentation where Active Ingredient and Substance are identical, after the XEVMPD Submission wizard was completed you received an XML file with one tag for the same Active Ingredient and one tag for the same Substance without duplicating data. However, for the same Indication/Intended Use and Indication value the generated XML file contained duplicate tags. This issue is resolved. One Indication/Intended Use value is present in the generated XML file when the same Indication/Intended Use Detail (non-Veterinary Product Detail Sets), or Indication Detail (Veterinary Product Detail Sets) is associated to several Product Detail Sets that are associated to one Full Product Presentation via Package Sets.
25605 [00056656]	6.2.0.0.0296	N/A	After an event was updated from a workflow, the list of products was not displayed in the Products tab under that Event. This issue is resolved. All associated products are displayed in the Products tab.
25561, 25535 [00056173, 00055825]	6.2.0.0.0296	25561 - 6.1.0.3.0115 25535 - 6.1.0.3.0111	When a multi-select extra field had more than one value and was included in a workflow, not all values were displayed for the field on the Activity page. This issue is resolved. The mechanism of processing the custom multi-select fields is improved to handle fields that contain multiple values.
25557; [00056104]	6.2.0.0.0296	6.1.0.3.0115	When attempting to save changes to a Product Family through a workflow, the error message `Cannot modify active ingredients on a Product Family that has associated Products` was generated. This issue is resolved. The appropriate validation process is improved and the Product Family can now be updated through a workflow.
25554; [00055924]	6.2.0.0.0296	N/A	When creating and associating a PDS using a Product Detail Set template, clicking the Save button more than once resulted in the PDS appearing to be associated with an Event multiple times. This issue is resolved.
25551, 25381; [00056031; 00054223]	6.2.0.0.0296	6.1.0.3.0120	When assigning an Activity or a Task to a user with a User Name containing a comma (,) character, the following appeared: The assigned Activity was not displayed in the My Activities tab invoked from GO TO > Activities or Navigation Pane > Activities. The Task Alert was not displayed in the Alert Center on the Calyx RIM Home Page. The system could not correctly interact with a database because the comma character was not included in the list of allowed special characters that can be processed during the execution of certain operations. This issue is resolved. The system has been updated to add the comma character to the list of allowed special characters that can be processed by the system.
25546; [00055951]	6.2.0.0.0296	6.1.0.3.0117	Due to the Internet Explorer one hour time out, the XEVMPD Audit Report was not returning data and was not responding in an acceptable time limit. This issue is resolved. The Calyx RIM 6.2 release improves performance of the XEVMPD Audit Report functionality.
25542; [00055861]	6.2.0.0.0296	N/A	When modifying a closed event, setting the Event Closed As field to `[Select]` and trying to save changes caused an invalid reference exception to appear and the event itself to become unavailable through any navigation paths. This issue is resolved. A new warning message is displayed stating that Event Closed As is a required field and must be specified prior to saving the changes.
25541; [00055826]	6.2.0.0.0296	6.1.0.3.0111	When completing an activity that required selecting a user field where the distinguished name was greater than 100 characters, the following error message was generated: `"! Exception while executing event-listener"`. This issue is resolved by allowing for distinguished name values up to 255 characters long.
25539; [00055840]	6.2.0.0.0296	N/A	When statuses are deleted from the Event-Country Attributes > Status Dates tab, the system should update both Actual Date and Projected Date attributes to have the `Null` value in the database. However only the `ACTUAL_DATE` (Actual Date) database value was updated correctly and the `SCHED_DATE` (Projected Date) value stayed unchanged. This issue is resolved. When the status is deleted, the `ACTUAL_DATE` and `SCHED_DATE` values are updated to have `Null` value in the event_country_status_schedule database table.
25538, 25495; [00052193, 00058004, 00056979, 00055469]	6.2.0.0.0296	N/A	There were performance issues observed when expanding the Assembly Tree nodes. The performance of expanding the nodes in the assembly tree and refreshing the expanded assembly tree has been improved. For more information on the new version of the assembly tree see Working with New Assembly Tree..
25536; [00055812]	6.2.0.0.0296	6.1.0.3.0116	A deadlock occurred in Calyx RIM when several workflow actions were performed when a long-running transaction (for example, lifecycle event) was in progress. When the workflow Activiti engine inserts a new row in a table in the Activiti schema, it uses an internal `DbIdGenerator` to generate the next ID value. The `DbIdGenerator` has a setting for `idBlockSize` that determines how many IDs to distribute before going back to the database for the next block. When a long-running transaction requested a new ID block, and then another transaction requested a new ID block before the first long-running transaction was committed, a deadlock occurred. This release reduces the possibility of a deadlock by increasing the default block size from 2,500 to 50,000. Also, this release enables the default block size value to be configurable by adding the following setting in the insight.var file specifying the appropriate block size: `activiti.blockSize=50000` Note: 50000 is a default size.
25526; [00055788]	6.2.0.0.0296	N/A	The `Yes` value set in the Publishing Settings Library > Default Values for the Use Native File attribute was not inherited by the leaf elements created automatically by associating documents with the folders. This issue is resolved. When the leaf is automatically created, the value set for the Use Native File attribute in the Publishing Settings Library is preserved.
25516; [00055405]	6.2.0.0.0296	6.1.0.3.0117	Updating the Publishing Settings to add or remove a DTD sometimes took much longer in Calyx RIM 6.2 compared to previous versions. This release improves the performance by causing Oracle to choose a better execution plan when updating Publishing Settings to add or remove a DTD.
25511; [00055024]	6.2.0.0.0296	N/A	In the Global Project Plan wizard, the manufacturers available for selection in the Manufacturer drop-down list were displayed in a random order for the following Update Product Detail Set Project > Add Manufacturer flows: Add Active Ingredient Manufacturer Add Active Ingredient Manufacturing Process Function Manufacturer Add Substance Manufacturer Add PDS Function Manufacturer This issue is resolved. The sorting mechanism has been added to display the Manufacturer values in the Manufacturer drop-down list in alphabetical order.
25510; [00055531, 00057192]	6.2.0.0.0296	N/A	For the following listed queries, the Substance Selection list (Search Criteria > Active Ingredient Name > Select) displayed all Active Ingredients from the Data Administration > Product Family Maintenance > Substance Values table: Product Detail Management > List of Active Ingredient Manufacturers Product Detail Management > List of Active Ingredient Function Manufacturers Product Detail Management > List of Active Ingredient Material Manufacturers Product Detail Management > List of Registrations with Active Ingredients Registration Planning and Tracking > List of Product Families In Calyx RIM 6.2, the Substance Selection list was reworked to display only Active Ingredients associated to the product families selected in the Product Family/Product Family Name multi-select list.
25508; [00055608]	6.2.0.0.0296	6.1.0.3.0111	In Calyx RIM for Analytics, the XEVMPD Audit Report returned duplicated results when a product was associated with more than one application. This issue is resolved.
25501, 25464; [00054523, 00054500, 00055108, 00054523]	6.2.0.0.0296	N/A	Performance issues were observed when the Ready for Submission wizard retargeted Reference Leafs for the entire Working View after the Assembly Plan was merged. This could cause the job to fail and the `Source leaf cannot be a reference leaf` error message to appear in the Job Details. The performance issue is resolved. The retargeting reference leafs system function is improved. The job is successfully completed and no error messages are displayed in the Job Details when the Ready for Submission wizard is finished.
25484; [00055433]	6.2.0.0.0296	6.1.0.3.0115	Volumes were created with blank names if the Assembly was volumized out of order. This issue is resolved. The mechanism of identifying the sibling volumes during the Bulk Volumization by Sheets operation has been improved.
25483; [00055072]	6.2.0.0.0296	6.1.0.3.0100	When in the Working View with Try New Version of an assembly tree option selected, using drag and drop to replace a document in a leaf with NEW status resulted in the leaf status not being automatically updated to REPLACE. This issue is resolved. The assign DMS nodes function is improved to refresh the assembly tree when the assign action is completed.
25481; [00055174]	6.2.0.0.0296	N/A	When requesting a DMS Synchronization from the Publishing View, all nodes from previous sequences were processed and that could take an extended period of time to complete. This issue is resolved. The performance of DMS Synchronization invoked from the Publishing View has been improved.
25475; [00054686]	6.2.0.0.0296	6.1.0.4.0041	Attempting to generate a volume TOC resulted in a `Failed to resolve TocEntry Name` error in the Job Requests window. The error `ORA-01438: value larger than specified precision allowed for this column` was also seen in the server.log.file. This issue is resolved. The precision constraint in the `ods.toc_entry.absolute_seq_no` column has been removed.
25469	6.2.0.0.0296		Attempting to delete a Dose Schedule PDS Detail resulted in an error. This issue is resolved.
25465	6.2.0.0.0296	6.1.0.3.0100	In Calyx RIM 6.1, an update trigger on the content table was modified to not create entries if the update was due to a renumbering event. The trigger, however, denoted updates to the content table as inserts instead of updates. The database script included with this release corrects the trigger and repairs affected data.
25461; [00055117]	6.2.0.0.0296	N/A	For the Canadian eCTD Module 1 v2.2, entering invalid numeric-only value for the Sequence Description field caused an `UndeclaredThrowableException` error message to appear in the publish Job Details. This issue is resolved. The revised message explains that numeric-only values are not supported for the Sequence Description field, and is displayed when you try to save the metadata.
25460; [00055109]	6.2.0.0.0296	N/A	When creating a New (Empty) Standalone Assembly, or a Standalone Assembly from an Assembly File using the New > Standalone Assembly option, the following fields were displayed as non-required: Publishing Settings Library Use Source Assembly Publishing Settings Library Saving those Standalone Assemblies without making any selections in the listed fields caused warning messages to appear. This issue is resolved. The fields are followed by an asterisk (*) indicating that they are required.
25457; [00055111, 00054917]	6.2.0.0.0296	N/A	In the unlocked Submitted View of an assembly you were unable to remove empty folders using the Delete icon on the Folder Attributes, if the Try New Version of an assembly tree option was selected. This issue is resolved. Now you can delete empty folders in the new version of an assembly tree.
25440; [00055119]	6.2.0.0.0296	6.1.0.4.0041	When creating a Working Assembly using the Create eCTD wizard, the error `ORA-00932: inconsistent datatypes: expected NUMBER got BINARY` occurred if the checkbox Update the sub-folder structure for was selected. This issue is resolved. The Create eCTD wizard can be finished successfully without displaying any errors.
25434; [00054636]	6.2.0.0.0296	N/A	When you selected the Create Missing Renditions and Extractions option for a PDF document with PDF Exists value set to `Yes` and Extractions Exist value set to `No`, the job was completed. However, the following message was displayed in the Job Requests details page: `No document to render`. This issue is resolved. An additional verification has been added for the Prepare to Publish. The system checks the Extractions Exist flag of a source document and the functionality now works as designed.
25422	6.2.0.0.0296	N/A	The following columns that display data related to Substance PDS Detail child entities were missing from the Product Detail Management > Application History and Product Detail Management > Application QC Status History queries: Application History Query: Substance Manufacturing Process Details Changed? Substance Manufacturing Process Function Details Changed? Substance Manufacturing Process Function Manufacturer Details Changed? Substance Manufacturing Process Step Details Changed? Substance Manufacturing Process Step Function Details Changed? Substance Manufacturing Process Step Function Manufacturer Details Changed? Substance Material Details Changed? Substance Material Manufacturer Details Changed? Application QC Status History Report: Substance Manufacturing Process Details QC Passed? Substance Manufacturing Process Function Details QC Passed? Substance Manufacturing Process Function Manufacturer Details QC Passed? Substance Manufacturing Process Step Details QC Passed? Substance Manufacturing Process Step Function Details QC Passed? Substance Manufacturing Process Step Function Manufacturer Details QC Passed? Substance Material Details QC Passed? Substance Material Manufacturer Details QC Passed? This issue is resolved. The appropriate values are now available for selection in the Display Columns multi-select field on the Application History Query > Enter Search Criteria and Application QC Status History Report > Enter Search Criteria pages. The appropriate columns appear on the Search Results page of both queries for the Substance PDS Detail related entities, when those columns are selected. The value presented in each of the columns is a hyperlink to the specific subreport.
25414; [00054605]	6.2.0.0.0296	6.1.0.4.0041	The `FLASHBACK_TIME=SYSTIMESTAMP` parameter was added to the `expdp` commands in the `dpexportinsight.sql` to keep all exported tables synchronised to the same point of time.
25410; [00055170, 00054235]	6.2.0.0.0296	6.1.0.3.0099	For US grouped submissions, the order of M1 metadata unintentionally affected whether or not the primary application was listed first in the published us-regional.xml. This issue is resolved. The primary application is always listed first in the `regional.xml`.
25405; [00054019]	6.2.0.0.0296	6.1.0.3.0093	For US eCTD v2.01 submissions: When using the Import eCTD to Application wizard (Import from eCTD icon on the Application attributes page) to import several sequences having 1.14.1.X subfolders introduced non-sequentially in different sequences, the nodes were not ordered numerically in the submitted view created by the import process. This issue is resolved.
25401; [00053089]	6.2.0.0.0296	6.1.0.3.0100	When the Rendition Identifier for an assembly document without a custom rendition was set to a non-standard value and the Use Standard Rendition option was selected for Missing Rendition Identifier Handling in Publishing Settings, Linking plug-in (PDF) was allowing you to create links in the standard rendition of the document instead of displaying an error as expected. This issue is resolved.
25395; [00054382]	6.2.0.0.0296	6.1.0.3.0092	When Calyx RIM attempted to create a DataExchangeExport file with the exact same timestamp-inclusive file name as an already existing export file, the duplicate name file would not be created. This issue is resolved by adding milliseconds to the timestamp portion of the filename to avoid duplicates.
25391; [00054454, 00054327, 00053609]	6.2.0.0.0296	`DB_hotfix6_1_0_chf3_0136.zip`	`ORA-01789` and `ORA-00942` errors occurred during the Calyx RIM6.2 CHF 3 migration when the AUD table had an obsolete column that did not exist in the corresponding table in the ODS/MGR/SEC schema. This issue is resolved and is no longer presented when migrating to Calyx RIM 6.2 from the previous Calyx RIM versions. Also, the `RULE` hint is added to improve the migration performance.
25379; [00054093]	6.2.0.0.0296	6.1.0.3.0092	When a Document with a Rendition Identifier that had been assigned to a document by default was later updated in the Working View of the Assembly to have any other Rendition Identifier value from Data Administration > DMS Integration > Rendition Identifier Values table, the change was not displayed in the Publishing View of the Assembly. However, in the published output the rendition was set correctly. This issue is resolved. During the document create or update actions, the list of specific attributes are copied from the Working View of an Assembly to the Publishing View. To have the Rendition Identifier value in the list that is copied to the Publishing View of an Assembly, the missing RenditionModifierTypeId value has been added to the system Copy function.
25376; [00054015, 00053356]	6.2.0.0.0296	N/A	Performance issues were observed when the system processed leafs in a sequence assembly within one application, for example converting a standard leaf to be a reference leaf. To fix the performance issue, the query has been optimized.
25370; [00053016]	6.2.0.0.0296	6.1.0.3.0100	When the jp-regional-index.xml file was replaced in Sequence 0001 and again in Sequence 0002, the index.xml file for Sequence 0002 referenced the 0000 regional xml file as the modified file instead of the 0001 version. This issue is resolved. For Japanese submissions, the method of searching for the sequence with the latest updated content is improved.
25361; [00054034]	6.2.0.0.0296	6.0.0.6.0027	If a Product Detail Set (PDS) had multiple approved Package Set details with approved Packaging details, the Product Detail Management > List of Registrations with Packaging query displayed each package set on the Search Results page, however only one Package Set was assigned to the Registration. This issue is resolved. The query Search Results page now displays only Package Set details associated to the Registration.
25358; [00053900]	6.2.0.0.0296	N/A	The Applicant Contact table for the US Module 1 eCTD v2.3 specification (DTD v3.3) Assembly > 1 Administrative Information folder displayed the Telephone and Email values as dimmed and unavailable, if: There were several Contact Telephone Number values with different telephone number types, but identical telephone numbers, assigned and one of them had been deactivated later on the Data Administration > Submission Maintenance > Applicant Contact Values > Applicant Contact Telephone Number tab. There were several Contact Email values assigned and one of them had been deactivated later on the Data Administration > Submission Maintenance > Applicant Contact Values > Applicant Contact Email tab. The issue is resolved: For Contact Email, only the deactivated value is displayed as dimmed and unavailable. For the Contact Telephone Number, the system checks the unique combination of the Telephone Number Type and Telephone Number values and indicates only the deactivated value to be displayed as dimmed and unavailable.
25348; [00054367]	6.2.0.0.0296	6.1.0.3.0117	In Calyx RIM 6.2, the queries related to the following areas have been optimized to reduce the possibility of database locks: Getting Events under Application Actions with the XEVMPD change history DTD change for an Assembly As part of this optimization, a new index has been added to the XEVMPD change history.
25345; [00053849]	6.2.0.0.0296	DB_hotfix6_1_0_chf3_0137.zip	The performance of the upgrade script that was used to migrate to Calyx RIM 6.1 CHF 3 has been improved. The DB_hotfix6_1_0_chf3_0137.zip upgrade script supercedes the DB_hotfix6_1_0_chf3_0136.zip upgrade script and must be used to migrate to Calyx RIM 6.1 CHF 3.
25333	6.2.0.0.0296	N/A	When setting up a notification for Registration FPP Attachment and selecting the When a value changes option to display the notification in the Alert Center, the notification was triggered. However, the entity URL on the Notification Attributes page displayed incorrectly concatenated data: Internal Name, Country, Attachment Name, and Attachment Version. This issue is resolved. The URL is displayed as a concatenation of Internal Name, Language, Attachment Name, and Attachment Version.
25324	6.2.0.0.0296	N/A	It was not possible to re-target a link that was already targeted to a bookmark. This issue is resolved.
25322	6.2.0.0.0296	N/A	When creating a new assembly using either the Existing Template, Assembly, or View option, the OK button on the Search Assembly Wizard remained unavailable after selecting the matching assembly. This issue is resolved. The OK button becomes active after you select the matching assembly and then click on Next.
25312; [00058254]	6.2.0.0.0296	6.1.0.4.0047	Attempting to delete a link from the Link Inspector results failed with an error. This issue is resolved. No error message is displayed when you delete a link from the Link Inspector results.
25309; [00054064; 00053322]	6.2.0.0.0296	6.1.0.3.0092	Calyx RIM 6.2 introduces a fix for Calyx RIM for Analytics to decrease the amount of time needed to load the Manufacturer Report page with the selection criteria. To improve the report performance, the PDS Name filter criterion has been removed from the Manufacturer Report filter criteria selection page. The PDS Name column on the report Search Results page is preserved.
25308; [00053352]	6.2.0.0.0296	N/A	In the Calyx RIM 6.1 CHF 1 and Calyx RIM 6.1 CHF 2 upgrade scripts, passwords from the `define.migration` file were stored and displayed in the resulting `master.sql` log file. The Calyx RIM 6.2 upgrade script resolves this issue.
25299; [00053287]	6.2.0.0.0296	6.1.0.3.0093	When assigning Withdrawal Time Unit values to the Species > Route of Administration > Withdrawal Times PDS Detail during the creation of a PDS Template, the Withdrawal Time Unit drop-down list displayed values that had been deactivated in Data Administration. This issue is resolved. The system has been enhanced to add a filtering option to the Species > Route of Administration > Withdrawal Times > Withdrawal Time Unit field that excludes the inactive values from the list.
25272; [00052896]	6.2.0.0.0296	N/A	After applying the upgrade script, importing the assembly template into Calyx RIM for the first time caused the following error message to be displayed: `The object you are acting on has been deleted or modified by another user. Refresh your object to view the current information.` This issue is resolved.
25268; [00052092]	6.2.0.0.0296	6.1.0.3.0089	Running the Update Status wizard from a Product Family Attributes page resulted in the unintentional changing of the Reviewing Country value for an application, when there was more than one country assigned. This issue is resolved. The reviewing country stays unchanged after the Update Status wizard is finished.
25266; [00052934]	6.2.0.0.0296	6.1.0.3.0089	Using the eCTD Import wizard to import an assembly that had a node-extension folder with hundreds of child leaf nodes took many hours to complete. This issue is resolved by separating one large import transaction into multiple smaller import transactions.
25264; [00052928]	6.2.0.0.0296	N/A	The M1 folder disappeared completely from the Assembly Tree during expand attempt if there were any nodes that contained a hyphen (‐) in the node name. This issue is resolved. This symbol is ignored in the New Assembly Tree. In addition, a specific script replace_soft-hyphen_with_minus.zip that is aimed to replace each instance of the hyphen across the Assembly Tree has been introduced. Please contact Technical Support for more information.
25246 [00052728]	6.2.0.0.0296	6.1.0.3.0092	Values in drop-down lists on the following Add PDS Detail pages were being sorted in a case-sensitive manner. Add Active Ingredient > Active Ingredient drop-down list Add Function > Function drop-down list Add Manufacturer > Manufacturer drop-down list This issue is resolved. The case of values is ignored during the sorting process.
25245; [00052399]	6.2.0.0.0296	N/A	Using the Update Status wizard for an Event with an associated Sequence caused an extra APPROVED Sequence status to appear in the Status Dates tab, when the Event was closed as WITHDRAWN or NOT APPROVED. This issue is resolved. The correct statuses are now displayed in the Sequence > Status Dates tab, when the Update Status wizard is passed.
25221; [00052338]	6.2.0.0.0296	6.1.0.3.0093	Running the Bulk Update Events wizard (launched from the Project Attributes page) when nothing was selected in the non-required Secondary Event Type field resulted in the Secondary Event Type values being cleared unintentionally for all applicable events. This issue is resolved. The Secondary Event Type values are preserved when the wizard is finished if this field has not been selected for modifications on the Select Attributes to update page of the wizard.
25215; [00052305]	6.2.0.0.0296	N/A	There was a performance issue in displaying a large quantity of users in Calyx RIM Security Administration. This issue is resolved: `ISM.DV_USER` view has been updated `ISM.R_SEC` package has been updated `lv_rc` line has been increased from VARCHAR2(4000) to VARCHAR2(32767)
25210; [00052191]	6.2.0.0.0296	N/A	There was a performance issue when logging on to Calyx RIM for Analytics. This issue is resolved. The following has been updated: An index `X2USR` has been added to the USR table, NAME field The `ISM.DV_USER_ACCESS_LEVEL` view has been updated
25209; [00053438, 00052279, 00052147, 00052137]	6.2.0.0.0296	hotfix6_1_0_chf1_0115.zip	The following error occurred during the Calyx RIM 6.1 CHF 1 migration: `ORA-01555: snapshot too old` This issue is resolved in the DB_hotfix6_1_0_chf4_0024.zip migration script that is used to migrate to Calyx RIM 6.1 CHF 4 from the previous Calyx RIM 6.1 CHFs. After performing the migration to Calyx RIM 6.1 CHF 4 and proceeding with the migration to Calyx RIM 6.2 using the appropriate migration script, no migration errors appear.
25206; [00051373, 00052844]	6.2.0.0.0296	N/A	If an assembly had been created from the existing Submitted View with the Retarget Copied Reference Leaf option selected, the following issues occurred: The Find Reference Leaf Elements option invoked on the Leaf element of the created assembly displayed the reference leaf elements of the copied submitted view. The created assembly could not be deleted. These issues are resolved: The Find Reference Leaf Elements option now displays the reference leaf elements of the current assembly. The created assembly can be deleted.
25197; [00052103]	6.2.0.0.0296	master.zip hotfix6_1_0_chf1_0115.zip	Data copied from a field in the `MGR.Application.Term_Withdraw_Reason` table to a field in the new `MGR.Term_with_reason_type` table that was too small resulted in the following errors: `ORA12899: value too large for column` `ORA-00001: unique constraint` This issue is resolved in the DB_hotfix6_1_0_chf4_0024.zip migration script that is used to migrate to Calyx RIM 6.1 CHF 4 from the previous Calyx RIM 6.1 CHFs. After performing the migration to Calyx RIM 6.1 CHF 4 and proceeding with the migration to Calyx RIM 6.2 using the appropriate migration script, no migration errors appear.
25182; [00051882]	6.2.0.0.0296	N/A	The Apache Commons Collections library was vulnerable to insecure deserialisation of data, which could result in arbitrary code execution. To fix this issue, the Apache Commons Collections version 3.2.2 has been applied to the Calyx RIM 6.2 Application Server. The Apache Commons Collections library version 3.2.2 mitigates the vulnerability by disabling the insecure functionality.
25158; [00051744]	6.2.0.0.0296	InsightForAnalytics.zip 6.1.0.3.0013 (InsightForAnalyics-6.1-chf3-hf1.zip ) WFConfig.zip 6.1.0.3.0009 (WFConfig-6.1-chf3-hf1.zip)	The log on to the Calyx RIM for Analytics failed if the Display Name contained the ampersand (&) character. This issue is resolved by escaping the ampersand characters for Display Name value in the wfsqlusers.fex and user_name.fex files.
25156	6.2.0.0.0296	6.1.0.2.0017	The error `ORA-02292: integrity constraint (ODS.R_789) violated - child record found` occurred when attempting to delete an application having a lifecycled assembly with a reference leaf. This issue is resolved.
25141; [00051550]	6.2.0.0.0296	6.1.0.3.0099	Attempting to import a Japanese submission having a `DELETE` operation in module 1 failed. This issue is resolved by updating the `xlink:href` attribute processing for the Leaf that has a `DELETE` status.
25140; [00051261]	6.2.0.0.0296	N/A	It was possible to delete a sequence with a working assembly that was created by another user, or in another tab. The Delete button on the Sequence Attributes page was enabled until the page was refreshed. This issue is resolved by adding an additional check to identify the presence of working assembly in the verifiable sequence. If the working assembly exists, the warning message is displayed.
25134; [00052137, 00051492, 00051212]	6.2.0.0.0296	hotfix6_1_0_chf1_0115.zip	During the migration from Calyx RIM 5.1 to Calyx RIM 6.1 CHF 1 the issue of an empty GUID column for leafs and folders was observed. This issue resulted in the following errors: `Error adding new not null constraint on FOLDER.GUID` `ORA-02296: cannot enable (ODS.) - null values found` `Error adding new not null constraint on LEAF.GUID` `ORA-02296: cannot enable (ODS.) - null values found` This issue is resolved in the DB_hotfix6_1_0_chf4_0024.zip migration script that is used to migrate to Calyx RIM 6.1 CHF 4 from the previous Calyx RIM 6.1 CHFs. After performing the migration to Calyx RIM 6.1 CHF 4 and proceeding with the migration to Calyx RIM 6.2 using the appropriate migration script, no migration errors appear.
25110, 25001; [00048772, 00049481, 00049976 , 00050201, 00050749, 00051273, 00051803]	6.2.0.0.0296	25110 - 6.0.0.5.0004, 6.1.0.2.0017 25001 - 6.0.0.5.0004, 6.1.0.2.0017	In Calyx RIM 6.1, if the default styles were not overridden, all native links were processed with the style obtained from the default link settings profile. This resulted in performance degradation of the publishing process. This issue is resolved with Calyx RIM 6.2, the functionality is modified by not altering native links unless the target page of the link is no longer in the same file due to a the file being split, or if the profile is not the default profile.
25091; [00049218]	6.2.0.0.0296	N/A	When Prepare to Publish, or Publish, was executed for a submission with any assigned documents that contained Xref links, you could experience an `UndeclaredThrowableException` error. This error was caused by Xrefs that are no longer supported by Calyx RIM. This issue is resolved: Xrefs are ignored and the link annotations are not created in the PDF rendition. All CDCXrefs in an in-process rendition, or PDF document, or rendition to be published, are always deleted. CDCXrefs no longer cause the publish request to fail.
25085; [00051005]	6.2.0.0.0296	N/A	When you created the Publishing Settings Library Template using the New > Publishing Settings Library Template option, one of the following issues occurred: Clicking Save after the session timeout, displayed the warning message: `You have already sent this request to the server. Please try again.` Clicking Save for the second time saved the entity. Navigating to the New > Publishing Settings Library Template option after the session timeout opened the Create Publishing Settings Library page, with the Publishing Library Owner field set to guest. Filling the attributes and clicking Save saved the entity. This issue is resolved. The system now does not allow you to save the Publishing Settings Library Template after the session timeout.
25075; [00050986]	6.2.0.0.0296	N/A	Navigating to Calyx RIM for Analytics while logged on to the Calyx RIM system caused the wrong user name value to be sent to the Calyx RIM for Analytics server. This issue is resolved. The system now uses the correct user name value for the SSO (Single Sign On) to the Calyx RIM for Analytics system.
25070; [00052810, 00051949, 00051259, 00050874]	6.2.0.0.0296	6.1.0.3.0093	When a user session expired, a guest account with no privileges was assigned to the session. Any subsequent action resulted in the login page being displayed. However, if the user was still idle when the guest session expired, errors were generated and logged in the `server.log` file. This issue is resolved. Calyx RIM no longer attempts to save settings for the guest user when the guest user session expires.
25058; [00050726]	6.2.0.0.0296	6.1.0.2.0015	Inactive functions were available for selection when executing the Add Active Ingredient Manufacturing Process Function Manufacturer step in the Global Project Plan Wizard > Update a Product Detail Set Project flow. This issue is resolved. Only Active functions are available for selection.
25054; [00050668]	6.2.0.0.0296	N/A	In email notifications, the old application logo was displayed and the Calyx RIM Manager notification system was indicated as the sender. This issue is resolved. The sender name is updated and is displayed as Calyx RIM notification system. The application logo is replaced with the most current one.
25045; [00050172, 00052819]	6.2.0.0.0296	N/A	The system allowed you to disassociate the approved Product Detail Set (PDS) with a withdrawn Shelf Life/Storage Condition detail from the Event, but the `ORA-02292: integrity constraint (MGR.R_732B) violated - child record found` error occurred. This issue is resolved. The system now does not allow the disassociation if there are data dependencies.
25014; [00050210]	6.2.0.0.0296	N/A	For sequence assemblies only, you could convert a leaf to be a reference leaf referencing itself, which violated the business rule that a leaf cannot reference itself. This issue is resolved. Now, if a user attempts to create a leaf referencing itself, the following error message is displayed: `A leaf cannot reference itself.`
25013; [00050091]	6.2.0.0.0296	N/A	When using the Recalculate Checksums option, the backbone files in the electronic output location were not updated if the electronic output location contained a normalized Application Code. Instead, new backbone files were published to the location which was 2 folders above the correct one, in case if during the normalization process the Application Code value was changed. This issue is resolved.
25002; [00050016]	6.2.0.0.0296	N/A	When creating a new assembly using Creating Assembly from a Template, Assembly, or View option or Import Assembly Wizard, data under the Sequence Assemblies tab was not appearing in a reasonable amount of time. This issue is resolved.
24959; [0004923, 00050581, 00051103]	6.2.0.0.0296	6.0.0.5.0008 6.1.0.2.0017	Long publishing time issues could occur due to Oracle choosing an inefficient execution plan for a particular query. This issue is resolved. The problematic query is rewritten to prohibit Oracle from choosing the inefficient execution plan.
24958; [00049474]	6.2.0.0.0296	N/A	When you opened the Assembly tab, a "Loading" message appeared but the operation was not completed in a reasonable amount of time for the Assembly Attributes page. However, the assembly tree and assembly tree elements were fully loaded and accessible. This issue is resolved.
24956; [00049263]	6.2.0.0.0296	N/A	When the Bulk Update Events wizard was invoked from the Project Attributes page, you could update the events with countries to which you had Read access. This issue is resolved. The Select Events to Update page now lists only events with countries, to which your access is set to at least Write.
24923; [00049174, 00049530]	6.2.0.0.0296	N/A	The 1.A.5 Comparison Table section in Thailand Module 1 Specification v1.0 had incorrect leaf output file name comparison.pdf. This issue is resolved. The leaf output file name is now appearing as comparison-table.pdf.
24896; [00048871, 00049238, 00024896, 00050205]	6.2.0.0.0296	N/A	When trying to extract a document with a bookmark that contained a non-Unicode character, the extract job was displayed as Completed. However, the Job Details contained an error with an exception, and the Assembly > Document Attributes had the Extract Exists field set to No. The issue with the job statuses is resolved. The correct status, Failed, is now displayed when a document is not extracted.
24891; [00047906]	6.2.0.0.0296	6.0.0.3.0037	Leafs and documents with names beginning with stf- were omitted during the eCTD Import process because the code interpreted all files located in study folders beginning with stf- as STF XML files. This issue is resolved.
24876; [00048681]	6.2.0.0.0296	6.0.0.3.0037	Attempting to remove a sequence from a lifecycle was not completing in a reasonable amount of time even after increasing the timeout value. The delay occurred due to the unnecessary calls to two queries. This issue is resolved.
24860; [00048499, 00054314]	6.2.0.0.0296	N/A	When using the eCTD Import process to import an assembly containing reference leafs that target leafs further down in the assembly tree, the reference leafs and target leafs were switched in the imported assembly. This issue is resolved for the region specific Module 1, and also Module 2, Module 3, Module 4, and Module 5 that are common for all regions.
24832; [00047932]	6.2.0.0.0296	5.1.0.5.0013 6.0.0.3.0034	Using the Import Assembly Wizard to import an assembly with the option to retarget selected reference leafs sometimes resulted in an invalid reference error. This issue is resolved.
24800; [00047397]	6.2.0.0.0296	6.1.0.3.0092	For null values on sequence `ACTUAL_DATE` fields from `01-JAN-1901` to `01-JAN-1900` the default date is set to avoid issues with incorrect event statuses appearing after migrations that set the values to dates between those two values.
24704	6.2.0.0.0296	N/A	The issue of incorrect display names for the Full Product Presentation and Registration FPP Attachment comment fields has been resolved: The Full Product Presentation Comments field has been reworked to be a display-only field on the View Full Product Presentation Attributes page. The Full Product Presentation Add Comment field has been added to the Create/Modify Full Product Presentation Attributes pages. The Attachment Comments field has been renamed to be Registration FPP Attachment Comments. See Fields Added: Calyx RIM 6.2 and Fields Updated: Calyx RIM 6.2.
24703	6.2.0.0.0296	N/A	The discussion thread related fields had the incorrect display names for the Product, Pharmaceutical Product, Event, Registration, and Sequence entities. This issue is resolved. To support the naming convention across the Calyx RIM system, the display names had been reworked to be: Product > Product Add Comment Pharmaceutical Product > Pharmaceutical Product Add Comment Event > Event Add Comment Registration > Registration Add Comment Sequence > Sequence Add Comment See Fields Updated: Calyx RIM 6.2.
24641	6.2.0.0.0296		When trying to delete a Product Details Set (PDS) with the child details added under the Substance node, the Delete button appeared dimmed after those details with Approved or Not Approved status had been deleted. This meant that the PDS could not be deleted due to data dependencies. This issue is resolved. The Delete button is now available and the PDS can be deleted.
24561	6.2.0.0.0296	N/A	The Next Renewal Date column on the Registrations tab was displayed incorrectly as First Renewal Date when you were navigating to it from the Product Family Attributes and Product Attributes pages. This issue is resolved. The column name is now displayed correctly for Product Family Attributes, Product Attributes, and Application Attributes pages.
24474; [00044014]	6.2.0.0.0296	N/A	A client reported a performance issue that appeared when changing the status to APPROVED for Event entities that were created as part of a migration. This issue has been resolved and is no longer reproducible on the latest Calyx RIM versions.
24422	6.2.0.0.0296	N/A	When using the Veeva DMS, an error occurred while attempting to bind a document to any label other than CURRENT. This issue is resolved. When the selected label is other than CURRENT, a warning message informs you that the document must be bound to a CURRENT label only.
24408; [00032393]	6.2.0.0.0296	N/A	The sorting for Manufacturer Details in the PDS tree was performed by the Manufacturer Status Date attribute. This issue is resolved. The Manufacturer Details are now sorted alphabetically.
22781; [00029737, 00044188]	6.2.0.0.0296	N/A	You were not able to modify the Active Ingredients field on the Modify Product Family page after the associated Product, that contained a Component, was deleted. This issue is resolved. Once the related Product along with its Component is deleted, the Active Ingredients field is displayed as a selection list and is available for modifications on the Modify Product Family page.
23690; [00051715, 00048203, 00047314]	6.2.0.0.0296	6.1.0.3.0084	Closing an event as Approved did not set the Application Status to Approved if the current Application Status value was Submitted. This issue is resolved.
22697; [00027525]	6.2.0.0.0296	N/A	When an Event was closed with a status of Withdrawn, all related Sequence Status Dates were changed to the withdrawn date. This issue is resolved. When an event is now closed, the Sequence will keep its status as well as the date for any sequence with a status of Approved, Not Approved, Submitted, or Withdrawn. If the Sequence status is Planned, it will be changed to Withdrawn.
22028; [198009FW]	6.2.0.0.0296	N/A	When changing the value in Product Family Type multiple selection field, refreshing of the List of Product Families page took several minutes. This issue occurred on all multiple selection fields across the system. This issue is resolved for Internet Explorer 11 and Google Chrome browsers.
20703; [144950FW, 00043370]	6.2.0.0.0296	N/A	You were not able to select multiple documents using the Shift and Ctrl keys and drag them within the assembly. This issue is resolved with the New Version of the Assembly Tree introduced in Calyx RIM 6.2.
18655	6.2.0.0.0296	N/A	Create eCTD wizard failed if many sets of metadata were applied. This issue has been resolved and is no longer reproducible on the latest Calyx RIM versions.