Calyx RIM Release Notes

Resolved Issues: Calyx RIM 7.0

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

If an issue was resolved in a previously released certified hotfix (CHF), that CHF build number is included.

Calyx RIM: Common

Issue CHF/Hotfix Build Description
26738;

[INC0056197]

N/A For some of the OOTB and extra fields of the newTextAreaView and adminTextAreaView types, the length limit was broken in the UI and after entering, the system showed only 50 characters in the UI. This issue is resolved.

Length in the UI is fixed and corrected for the OOTB and extra fields to show more than 50 characters.

26675 6.2.0.6.0022 Timeline/Event Plans did not work as expected when adding or removing a country from an existing Event Plan for MRP, DCP, or CP Procedure Types. Countries already associated with the existing Timeline/Event Plan were incorrectly listed in the Countries Available box and were not available in the Copy Default Lead Times from the following Country drop-down list. Also, when deleting countries from an Event Plan, no countries were listed in the Associated with Plan area. These issues are resolved to support the EMA XEVMPD requirement for BREXIT.
26673 6.2.0.6.0022 When Northern Ireland (XI) was added to the EU Region in Data Administration, the XEVMPD wizard did not recognize it and showed a warning message. This issue is resolved. The new Northern Ireland country is recognized as an in-scope country with a country code of XI for an XEVMPD submission to support the EMA XEVMPD requirement for BREXIT.
26672 6.2.0.6.0022 Northern Ireland could not be associated as a Registration Package set entity when added to the Product Detail Set, so country package set marketing information can be entered for EU CP Applications. This issue is resolved. Northern Ireland is associated as a Registration Package set entity when added to the Product Detail Set to support the EMA XEVMPD requirement for BREXIT.
26620 N/A The security issues related to the following vulnerabilities are addressed in this release:
  • XSS (Cross Site Scripting)
  • SSRF (Server Side Request Forgery)
  • FPT (Field-programmable Technology)
26619 6.2.0.6.0007 The System Process Default Flag was not available for Registrations > License Status. A workaround required you to use only one display status (not multiple) mapped to one Internal System Status value. This issue is resolved.
26617;

[INC0037885]

6.2.0.4.0079 Some words could not be saved, for example monkey in a text field, and an error message about invalid characters appeared. This issue is resolved. Words now can be saved to any text field in Calyx RIM 7.0 when enableXssFilter is set to true in the securityConfiguration.xml file.
26608;

[INC0038408]

6.2.0.5.0055 After migrating to Calyx RIM 6.2 CHF 4, clicking the Concerned Parties icon resulted in an error. This occurred if the domain of a user was changed and there was a NULL value for that user in the Domain column in the SEC.USR table. This issue is resolved.
26604;

[INC0037291]

7.0.0.0.0100 When a session was timed-out, trying to perform an activity resulted in the error message You do not have the appropriate privileges to access the requested resource. This issue is resolved. Now, if you try to perform an activity when a user session is timed-out, the user session will be restored.
26565;

[INC0033560]

6.2.0.5.0055 Calyx RIM did not recognize some users as members of their assigned Active Directory (AD) groups. This issue is resolved.
26486;

[INC0024081]

6.2.0.5.0055 If an application had an Active or Not Approved or Withdrawn status, and the application had a registration with a status other than Withdrawn, it was not possible to update an event with Withdrawn status. This issue is resolved.
26477;

[INC0023763]

N/A After Product Family information with its metadata was updated and then moved from Calyx RIM to D2 LSRD, subforms on the Properties tab were empty for the Application in D2 LSRD. When the Application information was updated separately in Calyx RIM, subforms on the Properties tab contained the appropriate information. This issue is resolved. The Propeties tab of D2 LSRD Application shows correct information when you update a Product Family or an Application in Calyx RIM.
26476;

[INC0029689]

6.2.0.6.0007 After the Product Family information and metadata were moved from Calyx RIM to D2 LSRD, making changes to Product Family Indications/Intended Use in Calyx RIM resulted in the deletion of the Submission Country value from D2 LSRD. In Calyx RIM, the application continued to display the Reviewing Country. This issue is resolved and the D2 LSRD shows all of the necessary information.
26449 6.2.0.5.0055 An InSight API request to retrieve a list of assemblies for assembly types other than templates did not work. This issue is resolved.
26402;

[INC0017878]

6.2.0.5.0055 When an event was closed with a reason using the Specify Reason for Termination/Withdrawal option, the same reason was applied to the parent application. This issue is resolved.
26397, 24517;

[INC0017263, 00044443]

6.2.0.5.0055 When deleting an assembly, there was no indicator to show the progress of the deletion process. This issue is resolved. A progress indicator shows that the deletion is in progress.
26388;

[INC0016307]

6.2.0.4.0079 In the Create Submission wizard Sequence Code field, despite entering a code of four digits as recommended, this message showed: If this is an eCTD submission it is recommended you enter a four digit sequence code. This issue is resolved. There are no messages when four digits are entered.
26367 6.2.0.4.0079 Calyx RIM retrieved only the first 999 groups when authenticating a user in Azure. As a result, users not in one of the first 999 groups were unable to log on. This issue is resolved. Calyx RIM now authenticates all users in Azure.
26346;

[INC0014465]

6.2.0.5.0055 Notifications were not sent even when the mail-service.xml file included a valid SMTP server name and port number. This issue is resolved.
26339;

[INC0014292]

6.2.0.4.0079 Calyx RIM failed to update the following via the API:
  • Historical or future dates in the Event Country Status Schedule
  • Projected and actual dates in the Sequence Status Schedule
These issues are resolved. You can now insert historical or future dates in the Event Country Status Schedule and the current actual date in the Sequence Status Schedule.
26323;

[INC0013607]

6.2.0.4.0079 If an assembly was created from another assembly, and the source assembly was removed from the system, manually adding an event to the Approved view resulted in the error: The object you are acting on has been deleted or modified by another user. Refresh your object to view the current information. In the Update Status wizard, trying to add an event to the Approved view caused Calyx RIM to freeze and the same error to be registered in the log file. These issues are resolved.
26316;

[INC0012933]

6.2.0.4.0079 Starting from Calyx RIM 6.1 CHF 4, the migration to 6.2 and CHFs failed with an ORA error in logs for some customers. This issue is resolved by removing the select * from dv_user_workflow_secure query from the migration package.
26307;

[CS0027071]

6.2.0.4.0079 When Calyx RIM was configured to use Single Sign-On via Microsoft Azure, a user disassociated from an Azure group added to Calyx RIM could not be re-associated back to that group. This issue is resolved.
26287;

[00012133]

6.2.0.4.0079 The New menu on the Calyx RIM home page displayed the following options only when access was enabled to more than one of the options in Security Administration. When access was enabled to only one of these options, that option failed to appear under the New menu:
  • System Alert
  • Publishing Settings Library Template
  • Change
  • Registration Attachment

This issue is resolved. Now, the New menu shows the option for which the access is enabled in Security Administration.

26278 6.2.0.4.0079 When e-signature was enabled for Azure AD users, the system accepted any user credentials for e-signature instead of the logged-in user credentials. As a result, anyone (including Read-only users) could sign in and save changes. This issue is resolved. Now, only logged-in users can sign in and save the changes.
26210, 25081;

[00064119, 00064088, 00063968, 00050671]

6.2.0.4.0079 Veeva users configured to use Single Sign-On (SSO) were unable to access DMS Browse because of authentication issues. This issue is resolved. Configuration for SSO authentication is now added to Calyx RIM for Veeva users. Veeva users can access DMS Browse without authentication errors.
26122;

[0063208 ]

6.2.0.4.0079 A role was not accessible on the Security Administration page if the role had all License Modules settings set to None/Select. This issue is resolved. Now, the No Module Users role is displayed as expected.
25941;

[00060258]

6.2.0.4.0079 Unauthorized remote users were able to access Red Hat JBoss EJBInvokerServlet. This issue is resolved by commenting the JBoss EJBInvokerServlet code block in the web.xml file. For more information, see Disabling Unauthorized Users from Accessing Red Hat JBoss EJBInvokerServlet.

Publishing

Issue CHF/Hotfix Build Description
26670;

[INC0045661]

N/A When an EAEU submission was published, the output file contained incorrect values in the <hcsdo:RegistrationFileIndicator> tag. This issue is resolved.
26625 6.2.0.6.0007 In the EAEU v 1.0 assembly template, some output folder values were missing and some output file names were incorrect. This issue is resolved.

Now, output folder values and output file names are updated as required.

26606;

[INC0038763]

6.2.0.5.0055 The Submission Readiness report took longer to generate than usual, and sometimes the report failed to generate. This issue is resolved. Now, the Submission Readiness report generates successfully in less time.
26597 6.2.0.5.0055 When EAEU submissions were published after performing a Delete operation on one or more leafs, incorrect leaf attributes and DocID values were included in the output XML. This issue is resolved. The output contains correct values.
26592 6.2.0.5.0055 The Export Published Output process did not support Cyrillic symbols in filenames when choosing to embed PDF files into the EAEU XML file. This issue is resolved.
26588 6.2.0.5.0055 The Export Published Output process failed intermittently when choosing to embed PDF files into the EAEU XML file when the processed file path included spaces. This issue is resolved.
26583;

[INC0023438]

6.2.0.5.0055 If a workflow was associated to the assembly root, a folder, or a document in an initial sequence assembly, and the Synchronize with the Submitted View option was applied, the workflow was lost. This issue is resolved. Associated workflows are kept for each node after the option is applied.
26582 6.2.0.5.0055 The mediaTypeCode attribute was missing from the embedded PDF nodes of the EAEU XML output file. Although this attribute is not required per the schema, the agency validator requires it. This issue is resolved. The mediaTypeCode attribute is now included in the EAEU XML file for embedded PDF nodes.
26556;

[INC0033264]

6.2.0.5.0055 When using the Synchronize with the Submitted View option, the time to synchronize the documents sometimes took longer than usual. This issue is resolved.
26537;

[INC0030024,INC0033088]

6.2.0.5.0055 All leaf Titles should have appeared in XML under the following conditions:
  • If a user published all XML from root assembly.
  • If an assembly had two leafs and one leaf is selected, Title for both leafs had to be published, not for only one. This condition did not work.
This issue is resolved. If all the XML is published from the root assembly, or if one of two leafs is selected and published, the system generates equal results in both cases.
26533;

[INC0029832]

6.2.0.5.0055 Errors were found when the Publishing Readiness Query was run for the China eCTD. This issue is resolved.
26530;

[INC0029543]

6.2.0.5.0055 The Document Creation Date showed the current date, even though no value was specified for that field in the modify mode. This issue is resolved. Now, Document Creation Date displays a date only when the field is populated.
26527, 26226, 25965;

[INC0029460, 00064445]

6.2.0.5.0055 The options For this Element and Document were not available on the Update Overlay Settings page invoked from the Document. This issue is resolved.
26502;

[INC0025226]

6.2.0.5.0055 Applying the eCTD Import to an AU-3-0 assembly where the Sequence Description attribute had a code values different from those provided by the agency caused the import to fail. This issue is resolved. Now the import ignores the mismatches and takes the code value.
26487;

[INC0024292]

6.2.0.5.0055 After importing published GCC submissions, some folders were renamed or missing. This issue is resolved. Now, the imported assembly keeps the original structure.
26469;

[INC0023438]

6.2.0.5.0055 If a Workflow was associated to a leaf in an initial sequence assembly and the Synchronize with the Submitted View option was applied, the Workflow was lost. This issue is resolved. Associated Workflows are kept for each leaf after the option is applied.
26458;

[INC0022479]

6.2.0.5.0055 Publishing failed for the 2.3.S, 2.3.P, and 2.7.3 folders of ICH Module 2-5 v3.2 when the metadata field contained a single quote character. This issue is resolved.
26455;

[INC0022252]

6.2.0.5.0055 Variables with spaces in the Variable Name field did not resolve in the published output. This issue is resolved.
26452;

[INC0015705]

26383;

[INC0015705]

6.2.0.4.0079 In an application containing single or multiple sequences, using the Create eCTD wizard from the Sequence page resulted in the Concerned Parties values getting deleted. This issue is resolved. The information of the Sequence Concerned Parties is displayed properly.
26444;

[INC0021105]

6.2.0.5.0055 Incorrect Folder/Leaf names were observed in sections 1.08, 1.09, and 1.12 in JP eCTD Module 1 v1.0 assembly template. This issue is resolved. The JP eCTD Module 1 v1.0 assembly template is updated.
26401;

[INC0017630]

6.2.0.5.0055 When deleting leafs in bulk using Delete (Withdraw) lifecycle operation in the Working assembly, the assembly tree refreshed and the deletion symbol (crossed leaf) appeared only on one of the leafs instead of all of them. This issue is resolved.
26438;

[INC0020386]

6.2.0.4.0079 The <sequence> value in published .xml output was not the same as the value defined for Sequence on the regional or envelope Folder Attributes page. This issue is resolved.

The value defined under the Folder Attributes page is displayed in the <sequence> tag for the versions of EU 3.0.1/3.0.3, JO-1.0 and GCC-1.5.

26434;

[INC0020054]

6.2.0.5.0055 In Internet Explorer, when using the Delete (Withdraw) option on multiple leafs from subfolders of a Working assembly, the process would run for a long time with no result. This issue is resolved. The method used to communicate with the server is changed and now you can select any number of leafs to withdraw.
26425;

[INC0376737]

6.2.0.5.0055 In a Working assembly with documents assigned from Documentum, the links created to bookmarks in other documents using Calyx RIM Linking plug-in (PDF) resolved to incorrect pages after publishing. This issue is resolved.
26422;

[INC0019310]

6.2.0.4.0079 Links with "Application" applicability were mixing (appeared where not necessary and disappeared where necessary) after DMS synchronization if the new minor version of the same document had been created in Documentum. This issue is resolved.
26409;

[INC0018167]

6.2.0.4.0079 The search function did not work in the Approved Views of an assembly. This issue is resolved.
26404;

[INC0018012]

6.2.0.4.0079 When a link was created to a bookmark in a document from a previous sequence, the link created targeted to the first page of the document, instead of the bookmark. This issue is resolved. Now the links target to the correct page.
26395;

[INC0016670]

6.2.0.4.0079 Folders in the approved view were out of order. This issue is resolved.
26386;

[INC0016091]

6.2.0.4.0079 A first request to create the parexel__c rendition for a PDF document from Veeva failed. This issue is resolved. The source document is retrieved instead of the parexel__c rendition if Standard Rendition is selected for a Veeva PDF file. For another Rendition Identifier value and non-PDF documents, the corresponding rendition is used. Now, in some cases two calls instead of three are sent to Veeva.
26370;

[INC0015274]

6.2.0.5.0055 The pagination formulas using Reverse and Bates types did not resolve properly for paper publishing. Example:$Bates($Reverse($Calculate(${ATP}-${ARP}+1),"-1"),5).
This issue is resolved. The formula works when an intermediate variable is used as the first one in alphabetical order according to Variable Code. Example:
  • Variable Name = someTestName, Variable code = calcRevPage,Variable Value = $Reverse($Calculate(${ATP}-${ARP}+1),"-1")
  • Variable Name = someTestName , Variable code = revBates, Variable Value = $Bates($calcRevPage, 5)
To experience better performance, we recommend to minimize the formulas usage and set up them in Publishing Settings Library, not in Data Administration.
26361;

[INC0014994]

6.2.0.4.0079 Leaf attributes were missing from a leaf in the Approved View when that leaf was replaced in a previously lifecycled sequence. This issue is resolved.
26344;

[INC0014379]

6.2.0.4.0079 On the Add or Edit Page Marker menu, changing the Page Number to more than 3 characters caused the error message: Page Number cannot exceed 3 characters. This issue is resolved. Now, it is possible to enter 5 characters in the Page Number field.
26340;

[INC0014300]

6.2.0.5.0055 After reordering leafs in a Working Assembly using Reorder Child Leafs option, users observed empty folders in Publishing and Sequence views. This issue is resolved in InSight 6.2 CHF 4 as a result of other fixes.
26328;

[INC0014090]

6.2.0.4.0079 When the lifecycle operation on the same leaf across different sequences was performed and those events were added to the Approved View, using the Change Status Wizard resulted in an error. This issue is resolved.
26320;

[CS0042776 ]

6.2.0.4.0079 Users authenticating with Azure AD were unable to access Veeva using Single Sign-On (SSO) when Veeva was configured to authenticate using ADFS. This issue is resolved.
26310, 19440;

[INC0012460]

6.2.0.5.0055 After performing a DMS Synchronization on an assembly with an assigned document that was versioned, the document attributes and assembly tree were not automatically refreshed by Calyx RIM. This issue is resolved. Now, the icon 'Newer version available' is displayed without having to manually refresh the assembly tree.
26300;

[00063883]

6.2.0.4.0079 After an EU MRP assembly with an updated folder structure different from the template order was lifecycled, the Sequence view displayed empty folders in the next Working assembly after Create eCTD wizard was launched. This issue is resolved. Now, the Sequence view does not include any empty folders.
26291, 26410;

[INC0012181, INC0018227]

6.2.0.4.0079 In a working assembly, performing a Replace operation on a reference leaf failed to load the assembly tree. This issue is resolved.
26286;

[INC0012051]

6.2.0.4.0079 Retrieving a list of assembly templates via API requests failed. This issue is resolved. Now, the list of assembly templates via API requests can be accessed successfully.
26276;

[INC0011104]

6.2.0.5.0055 The assembly templates for CH 1.3 and CH 1.4 contained errors that caused validation issues. This issue is resolved.
26255;

[00065020]

6.2.0.4.0079 Creating a standalone assembly using the JO 1.0 assembly template and then executing the Create Study Reports wizard failed with the cannot determine region based on dtds error. This issue is resolved. The Create Study Reports wizard now runs successfully, and you can create a standalone assembly using the JO 1.0 assembly template without error.
26247, 26405;

[00064107, 00016162, INC0018046]

6.2.0.4.0079 When a document from a Veeva repository was assigned, the rendition information was recognized incorrectly by Calyx RIM. This resulted in an unnecessary extract request. If a TOC had Calyx RIM bookmarks that were edited, the edit changes did not appear in the generated TOC. Also, an extraction request was sent with each rendition, even when the rendition parameters were not changed. These issues are resolved. When documents are assigned from a Veeva repository, the rendition information is recognized correctly and edits appear correctly in the generated TOC. If rendition parameters are not changed, no extraction request is sent.
26245;

[00065009]

6.2.0.4.0079 Calyx RIM authentication via API failed when an application server was configured with multiple domains. This issue is resolved.
26240;

[00064944]

6.2.0.4.0079 When replacing a leaf in a subsequent sequence associated with a new event, closing the event and creating an approved view, both the new leaf and the replaced leaf were displayed in the approved view. This issue is resolved. Only the replaced leaf is displayed in the approved view.
26221;

[00064631]

6.2.0.5.0055 In EU Submissions with MAA in Submission Type and with the initial value in Submission Unit Type, the users were able to save the empty INN in EMA Envelope Information. This issue is resolved. Now, the users are required to populate it when needed.
26199;

[00064147]

6.2.0.4.0079 After updating a template and running Render Generated TOCs and Special Sheet Templates, extractions were generated for each assembly element containing a special sheet if it pointed to the same template and there were multiple settings profiles with the same template file. This issue is resolved. Now, the extraction request is sent for each special sheet template.
26163;

[00063867]

6.2.0.4.0079 The folder structure of study reports created when importing an eCTD application was incorrect. This issue is resolved. The folder structure of study reports is now created correctly when importing an eCTD application.
26142;

[00063604]

6.2.0.4.0079 When using the Volumize feature on an assembly that contained a volume with a TOC attached to it, there was an error. This issue is resolved. Now, using the Volumize feature on an assembly containing a volume with a TOC attached to it does not display an error.
26139;

[00063733]

6.2.0.4.0079 Creating a new assembly, or importing using an existing assembly, took longer than expected. This issue is resolved. The performance of creating a new assembly, or importing an assembly using an existing assembly, is improved.
26137;

[00062685]

6.2.0.4.0079 An invalid reference error occurred when changing the XML definition file in the publishing settings from U.S. 2.0.1 to U.S 3.3, if more than one application type with the same us-3-3 Application DTD/Schema and eCTD code existed. This issue is resolved. Now, no error shows when changing the XML definition file in the publishing settings from U.S. 2.0.1 to U.S 3.3.
26120;

[00063566]

6.2.0.4.0079 When an assembly section was selected in the Import Assembly Wizard, or when an assembly was created from an existing assembly, the corresponding assembly tree sections at the bottom half of the page were not displayed. Also, the full length of the scroll bar was not displayed, even on a maximized browser window. These issue are resolved. When an assembly section is selected in the Import Assembly Wizard. or when creating an assembly from an existing assembly, the corresponding assembly tree sections are displayed. The full length of the scroll bar shows on the browser window.
26057;

[00063029]

6.2.0.4.0079 The Reset TOC Content button was not enabled in assemblies unless the Standalone Assemblies value for home page access under Security Administration was set to Yes. This issue is resolved.
26046;

[00062700]

6.2.0.4.0079 The performance of refreshing the Link Inspector took several hours. This issue is resolved. The performance has been improved in sequence assemblies with:
  • External links in documents when source and target are within the same tree
  • Internal links in documents
  • In-Process links in documents
25979;

[00060743]

6.2.0.4.0079 When the screen resolution was set lower than [X]x1050 format, users were not able to send a publish request because the OK and Cancel buttons on the Publish Request and Job Details windows were not visible. This issue is resolved.
25862 6.2.0.4.0079 In an assembly tree, after running Prepare to Publish, deleting a leaf containing a source document linked to a target document resulted in a warning: ORA-02292: integrity constraint (ODS.R_339) violated - child record found. This issue is resolved. A leaf is deleted successfully.
25831 6.2.0.5.0055 When using the API to convert a leaf to reference, it could not be targeted to a leaf from a Sequence view. This issue is resolved.
25566;

[00054314]

6.2.0.4.0079 When using the eCTD Import process to import an assembly containing reference leafs and assigned documents in the assembly tree, the reference leafs and the documents were switched in the imported assembly. This issue is resolved.
25487;

[00055381]

6.2.0.5.0055 The Find and Replace option did not function as expected in the Publishing view of an assembly and the updated leaf names were not available in the current sequence in the Working view. This issue is resolved. Now, in the Publishing view, the Find and Replace option updates the nodes as expected in the current sequence in the Working view.
25263;

[00052834]

6.2.0.5.0055 GCC submissions containing multiple Cover Letters could not be imported to Calyx RIM. This issue is resolved.
23864;

[00039884, 00054020, 00055522, INC0016252]

6.2.0.5.0055 Using the Change Submittal Status wizard after changing a folder extension in a later sequence caused a reference error. This issue is resolved.
25325;

[00053635, 00055122, 00059463, 00062975,INC0016253, INC0016254, INC0017802]

6.2.0.5.0055 GCC sequences failed an eCTD import because of missing language folders in xlink:href. This issue is resolved. Now, the eCTD import is completed with no errors in the Job Requests even if language is missing for some folders. The system takes the English language as the default one and the language folder name is the same as in GCC template.
23864;

[00039884, 00054020, 00055522, INC0016252]

6.2.0.5.0055 Using the Change Submittal Status wizard after changing a folder extension in a later sequence caused a reference error. This issue is resolved.

Registrations

Issue CHF/Hotfix Build Description
26447 6.2.0.4.0079 On the Product Family Attributes page, the following attributes were incorrectly listed after the Development Sponsor attribute. This issue was specific to the Pharmaceutical, Veterinary and Flu Vaccine product family types. This issue is resolved. Now, these attributes are listed after the Approved Trade Names attribute.
  • Product Family Concerned Parties
  • Product Family Keywords
  • Product Family Description
  • Product Family Comments
26419;

[INC0019054]

6.2.0.4.0079 When a Package Set was associated with a Registration instead of with a Full Product Presentation (FPP), the information from the PDS Active Ingredients of the Package Set was included in the submission XML. This issue is resolved. Only Active Ingredients from Package Sets associated with a Full Product Presentation are now included in the XEVMPD submission XML.
26417;

[INC0018864]

6.2.0.4.0079 An Application was not updated with the Withdrawn status despite the Registration License Status value being internally mapped to Withdrawn. This issue is resolved.
26398;

[INC0017367]

6.2.0.4.0079 When using the Copy Registration Wizard, trying to copy a registration in a multiple country application such as an MRP or DCP resulted in an error. The error was due to the constraint on the Medicinal Regulatory Agency field. This issue is resolved.

After using the Copy Registration Wizard, the field Medicinal Regulatory Agency becomes blank and the value must be updated manually.

26227;

[00064595]

6.2.0.4.0079 If the time of the Approved status was set to a time that was earlier than that of the Submitted status, the status in the Event attributes page in the Countries tab changed to Submitted. This issue is resolved. Now, the calculation of Event Country Statuses is corrected. The current status shows the latest actual date.
26193;

[00064402]

6.2.0.4.0079 In the Registration Attachment page, selecting a file that had an extension in upper case (such as .DOC or .PDF) failed to populate values for the Attachment Name and the File Name fields. This issue is resolved. Values for Attachment Name and File Name fields are populated as expected.
26127;

[00063568]

6.2.0.4.0079 The URL in the e-mail that was sent to concerned users when an Event-Country Status was changed, failed to resolve to the expected target. This issue is resolved. Now, clicking the URL navigates to the event country where the status was created or updated.
26063;

[00062715]

6.2.0.4.0079 The query for the List of Product Registrations with Application and Product Detail Properties report failed to show the results on the screen. This issue is resolved. Now, the query for the List of Product Registrations with Application and Product Detail Properties report shows the results on the screen.
25996;

[00060206]

6.2.0.4.0079 In the Global Project Plan (GPP) wizard, selecting multiple events that exceeded the query limit resulted in the disappearance of the Update Project Event Country Status field, in some cases. This issue is resolved. The SQL query limit is increased for Event Country Status field in GPP wizard Update Project Event Country Status flow.

XEVMPD

Issue CHF/Hotfix Build Description
26336;

[INC0014237]

6.2.0.4.0079 The XEVMPD Submission wizard worked incorrectly for the Invalidate MA operation type on an Authorised Product when there was more than one Event and this resulted in the error: No Active Ingredient was specified. This issue is resolved. For the Invalidate MA operation type on an Authorised Product, when there are multiple Events for the same PDS, the XEVMPD Submission wizard works correctly.

Workflows

Issue CHF/Hotfix Build Description
26195;

[00064087]

6.2.0.4.0079 When an activity name was longer than 255 characters, trying to complete that activity resulted in an error. This issue is resolved. Now, an activity name can contain up to 1000 characters.
25990;

[00060779]

6.2.0.4.0079 When creating an Event-Country Status under a closed Event that was created via a workflow, there was an error. This issue is resolved. Now, there will be no error when creating an Event-Country Status under a closed Event that is created via a workflow.

Rendering

Issue CHF/Hotfix Build Description
4999;

[INC0040253]

4.4.1.1 Inserting a metafile (.emf) conflicted with the Amyuni printer driver and caused the rendition to fail. This issue is resolved. It is recommended that you convert any .emf file to a different format before inserting to prevent rendition issues.
4998;

[INC0037216]

5.0.0.17 When a large file from Veeva DMS was assigned to an assembly and published, the publishing process failed with the System out of memory error. This issue is resolved. Now, large files from Veeva DMS assigned to an assembly publish successfully.
4997 4.4.1.1 After rendering Word documents, some links in the rendered PDFs were sometimes split into multiple link boxes. This issue is resolved. Now the links are displayed correctly.
4991;

[PRB0040598]

4.4 CHF 2 Some native links could disappear under certain conditions, such as splitting a document in an assembly into several page ranges. This issue is resolved. Now the links are displayed and navigate to the correct locations.
4988 N/A The Business Service Retrieve re-authenticated with Veeva on each request processed and caused the Veeva API burst limit to be reached. This issue is resolved. Rendering now includes a cache that saves login data so that it does not have to authenticate each time it needs to get a document or information from Veeva.
4979 4.4.1.4 Publish jobs failed when attempting to publish two documents assigned from Veeva with Publishing Output Channel = Paper. This issue is resolved.
4975, 4928, 4895;

[00056617, 00062932, INC0016169, INC0021914]

4.4 CHF 2 Print jobs using the Liquent PS Printer option failed due to memory management issues in the third-party component responsible for converting PDF to Postscript. This affected Postscript-based printers only. This issue is resolved.
4958;

[00056740, INC0013561]

4.4 CHF 2 Watch requests failed if the server they belonged to was down or suspended. This was caused by a problem with the repository backup algorithm. This issue is resolved. Now a backup repository will properly execute watches that belong to a down or suspended repository.
4946;

[00064768]

4.4.0.49 Rendering was not able to communicate back to the application server on networks that did not allow TLS 1.0 encryption. This issue is resolved.
4945;

[00064279]

N/A Thai and other scripts that depend on combining diacritics had those diacritics incorrectly placed on printed tabs. This issue is resolved. Thai text is correctly printed on tabs.
4929;

[00062908]

4.4 CHF 2 Issues with the Auto Text Wrap option for tabs caused improper line breaks, which required the manual override of tab text. This issue is resolved by an expanded list of line break symbols.
4889;

[00055307,00058062, 00060015, 00060371]

N/A The maximum file size that could be retrieved for publish or render is 2 GB. To publish or render successfully, it was recommended to divide the files larger than 2 GB to smaller files and save. This issue is resolved. Now, you can retrieve files that are larger than 2GB for publish or render.
4850; [00052462] 4.4.1.1 Rendering limited the number of sub-jobs to 25 per workflow and would not start the next workflow until all 25 sub-jobs had completed. This issue is resolved. Now, the total MaxConcurrent for the Workflow Business Service on all servers is multiplied by 3 to control the number of jobs in progress, with 10 as the minimum and 40 as the maximum. Examples:
Servers Maximum concurrent Formula value Jobs in progress
2 servers 3 10 (low limit) 3
2 servers 15 10 (low limit) 10
4 servers 5 12 (4*3) 5
4 servers 15 12 (4*3) 12
20 servers 5 40 (high limit) 5
20 servers 50 40 (high limit) 40
4767;

[00056042, 00048240, 00050634, 00055970, 00058496]

4.0.0.96 Rendering Microsoft Word and Excel documents containing objects that reference external sources is not supported by the Rendering platform. To prevent such job requests from failing, this update suppresses errors associated with such objects and allows rendering of documents containing such content to complete successfully, although rendition fidelity is not assured.
4639;

[00041423]

4.4 CHF 2 Large jobs sometimes failed and showed the error message, "Not enough storage is available to complete this operation." Tickets are now optimized to reduce their size.
4592 4.4.0.51 Publishes with many small distribute requests (as in NeeS or leaf-only publish submissions) failed intermittently with the error: "Unable to distribute folder". This issue is resolved.