Skip to main content

V16 release notes

This topic contains the V16 release notes for . The release notes are organized into these high-level sections:

To identify if a feature request you made was included in this release, search these release notes or the release note archive for the work item number that Customer Support gave you. The release notes include a work item number for every new feature, updated feature, and defect fix.

As this page is maintained and updated over time to ensure accurate and timely information, recommends referencing the release notes online rather than printing and referencing static versions of the page. The Changelog page lists all notable changes made to this page.[Release notes changelog]

Installation and upgrades​

The V16 release can be installed with the at http://install.komodohealth.com/products/mic/16.0.0.32. New installs of will be on the latest release while current customers will need to run and deploy the latest update.

Warning: Remember to complete the steps in the Required pre-install & pre-upgrade actions section below as appropriate.

New features​

The V16 release of contains several new features whose functionalities are detailed below. Details about enablement and configuration are included within the product documentation.

New Adverse Event Child Record component​

The MIC - Adverse Event Child Record (medAdverseEventChildRecord) Lightning Web Component is a new component for managing the child records of Adverse Event (MED_Adverse_Event__c) records. Previously, users had to create new Adverse Event child records in a modal, which prevented the users from accessing other information on the parent Adverse Event record. With the new component, users can create new child records directly on the Adverse Event record page and therefore reference any related information on the parent record or on any other child record. Admin users must configure the component for each child object and can specify the fields to appear, the name of the component, and more. For product documentation, including configuration options, reference Adverse Event Child Record.

Related work item(s): MIC-4000, MIC-4008

Files Connect with Google Drive​

now has an integration with Google Drive through Salesforce's Files Connect service that enables users to create, reference, and collaborate on files that are hosted externally. The files can be Microsoft 365 files, Google Drive files, and other text and image files stored in Google Drive up to 6MB in size. Users can also create snapshots of the files to track changes. For product documentation, including setup and configuration steps, reference Files Connect.

Warning: External files created with the Files Connect integration are not supported for fulfillments.

Related work item(s): PLTFM-3034, PLTFM-3037, PLTFM-3075, PLTFM-3096, PLTFM-3107, PLTFM-3108, PLTFM-3109, PLTFM-3116, PLTFM-3127, PLTFM-3136, PLTFM-3149, PLTFM-3162, PLTFM-3168, PLTFM-3193, PLTFM-3201

Updated features​

The V16 release of also contains several improvements and optimizations to existing features and functionalities to better align with customer feedback and provide an enhanced user experience. Unless noted otherwise, all updated features are shipped "off" by default for existing customers and "on" by default for new customers.

Updated Account Search V3​

Account Search V3 has been updated to include several enhancements to existing functionalities as well as improvements to the user interface and user experience (UI/UX).

Configure default Quick Search options like account type filters​

Both the MIC - Case Accounts (MED_CaseAccounts) component and the MIC - Case Accounts Quick Search (medCaseAccountsQuickSearch) component have additional default options that admin users can configure, such as the ability to show or hide the Omni Search box, the Country field (which, as described below, is no longer required), the Account record type filters, the Advanced Search fields, and the Restrict toggle. This enhances the usability of the components, especially the option to let users filter by specific Account record types while searching for an account. Previously, users had to first perform an account search before they could filter the search results by account types like HCPs, non-HCPs, or employees. Now, users can select an account type in the initial account search as long as the Account Search component is appropriately configured. For product documentation, reference Configure default visibility.

Related work item(s): MIC-3923

Secondary information in search results​

Users are now able to view secondary, or additional, information about each account in the search results by hovering over or clicking the down arrow to the right of any account. A popover will appear and, by default, show the account's source, credentials, primary language, and specialty for both person accounts and institution accounts. Admin users can configure the fields that should appear as secondary information as well as hide the secondary information popover completely. For product documentation, including configuration steps, reference Configure secondary information.

Related work item(s): MIC-3938

Country field no longer required​

The Country field is no longer required in Account Search and Account records. Previously, while users could set the Country field to equal None when searching for an account, Account Search would still use an associated Country value, such as that on the related Interaction record, to query for Account records. Now, if the Country field is None, null, or empty, then a global (ZZ) account search is performed. This ensures that users can search for and create accounts without selecting a country. This also means that the Country field can be removed from Account Search layouts. However, if the Country field is removed from a layout, then the State field, which is dependent on the Country field, must also be removed from the layout to avoid any potential errors.

Note: This will be "on" by default, and no steps are required to enable this enhancement.

Related work item(s): MIC-3955

Visual updates on the results table​

The results table has a few visual enhancements, including updated column names, disc-style lists in contact and affiliation columns, highlighted icons for the selected account, and padding between each distinct value in a row. Additionally, the data in each column no longer appears cut off and instead automatically wraps to the following line if it does not fit in the default column width. This improves user readability by ensuring that the data returned by Account Search fits inside the columns in the results table.

Note: This will be "on" by default, and no steps are required to enable this enhancement.

Related work item(s): MIC-3873, MIC-3968

Inactive records excluded from search results​

Account Search now automatically excludes Account, Contact Information (MED_Contact_Information__c), and Affiliation (MED_Affiliation__c) records that have a Status (MED_Status__c) value of Inactive to provide users with the most relevant search results. Previously, Account Search returned both active and inactive records, which admin users can revert to in the new release via the Global Setting (mvn__MED_Global_Setting__mdt) custom metadata type. On the new Account Search Excluded Statuses (mvn__MED_Account_Search_Excluded_Statuses__c) field, admin users can configure the statuses that should be excluded, which will subsequently override the new default Account Search behavior of only returning active records. For example, to filter out both inactive and pending Account, Contact Information, and Affiliation records, an admin user must set the Account Search Excluded Statuses field to Inactive,Pending, not just Pending. For product documentation, reference Results table.

Note: This will be "on" by default, and no steps are required to enable this enhancement.

Related work item(s): MIC-3975

Auto-scroll to search results​

When users conduct an account search in either the Account Search tab or the Quick Search component, Account Search will automatically scroll down to the results. This helps users more quickly access their desired search results.

Note: This will be "on" by default, and no steps are required to enable this enhancement.

Related work item(s): MIC-3986

A new Back button is available in the top left corner of the Account Search tab for users to navigate from Account Search back to the Interaction record. Previously, users had to either close the Account Search tab and lose their search in progress and/or find and click the Interaction tab among other open tabs. Now, users can more easily navigate between the two tabs.

Related work item(s): MIC-3987

Add Fulfillment Files List component to other objects​

Admin users can now add the MIC - Fulfillment Files List component to the record pages of other objects, such as Adverse Event (MED_Adverse_Event__c), Request (MED_Request__c), and PQC (MED_Product_Quality_Complaint__c) pages. This allows users to more easily manage fulfillment documents across the product, including checking in/out, finalizing, and deleting documents.

Related work item(s): MIC-4003

E2B updates​

Admin users can now set null values more explicitly without needing to worry about issues with nullFlavors. For example, if a person's initials are UNK, they would be sent as Unknown instead of keeping the valid initials. Additionally, no longer substitutes plain nullFlavor values like MSK for the nullFlavor syntax. Instead, these will be allowed as values.

To set a nullFlavor, admin users should map a value of nullFlavor_\<null flavor value\>. The specified value will be set as the special nullFlavor attribute for the attribute.

Additionally, the MED_E2B_Generate_Button value has been updated from Generate to Yes. Submit AE while the MED_E2B_Generator_Header label value has been changed from E2B (R3) Generator to Submit Adverse Event.

Related work item(s): MIC-3988, MIC-4009

Complete a task for another user on the Task record​

Admin users can now configure the new ✓ Complete Task button to appear on Task records. This enables users with the required permissions to complete workflow tasks directly on the Task record on behalf of a task assignee. Previously, if a user wanted to complete a task in place of an assignee, the user had to mark the task as complete on the Document record because they could not do so on the Task record. With the new release, users can complete tasks both on the Task detail page and the Document record page.

Related work item(s): PLTFM-2961

Reassign a task to another user​

Users are now able to reassign their workflow tasks to other users without needing administrator access. Previously, users could not reassign their workflow task unless they had the CM_Admin custom permission or asked another user who had the CM_Admin custom permission. In the new release, users can just be assigned the new CM_Reassign_Task custom permission, which is included in the CM_ReassignTasks permission set. For product documentation, reference Reassign tasks.

Related work item(s): PLTFM-2931

Search with multiple characters in picklists and comboboxes​

Picklists and comboboxes previously only allowed single-character searches. This meant that when users entered multiple characters, each character was interpreted as a new search. For example, if a user typed fr in a picklist field with language options, the picklist would first scroll to the values that start with f and then scroll to the values that start with r. In the new release, however, every multiple-character search in picklists and comboboxes is treated as a single filter query. For example, if a user types a fr in a picklist field with language options, the user will be shown values that start with fr, like French.

Note: This will be "on" by default, and no steps are required to enable this enhancement.

Related work item(s): PLTFM-2979

Hide file hosting options in New Document wizard​

Each of the file hosting options in the New Document wizard can be hidden via new fields on the MCM Global Setting (mvn__CM_Global_Setting__mdt) custom metadata type. This enables admins to have greater control over the types of documents that users can create in . For product documentation, reference MCM Global Setting.

Related work item(s): PLTFM-3034, PLTFM-3094

Track the original document of cloned documents​

When a document is cloned, users are able to use the new Cloned From (mvn__CM_Document__c) field on the Document (mvn__CM_Document__c) object to more easily track the original document.

Related work item(s): PLTFM-3276

Defect fixes and maintenance​

The following table details defects and maintenance items identified in V15 that are fixed in the V16 release.

Fixed items​
Work itemDescriptionNew behavior
MIC-2753The MIC - Enhanced Record Edit (medEnhancedRecordEdit) component used the getRecordUi wire adapter for the user interface (UI), which Salesforce has deprecated.The MIC - Enhanced Record Edit component uses getLayout instead of getRecordUi.
MIC-3905When a G.K.7.r.1 E2B output was generated, a performer tag was missing, resulting in it being missed by safety systems.A performer tag has been added to G.k.7.r.1/2.
MIC-3911The Account lookup field on an Interaction (Case) record was editable when users tried to update the account's contact information, such as their email address.A validation rule has been added that disallows changing the selected account's contact information.
MIC-3918When there were long or rich text fields in an Account Search query and any single account in the search results had more than 200 related Contact Information (MED_Contact_Information__c) or Affiliation (MED_Affiliation__c) records, the search would throw the following error message: "Aggregate query has too many rows for direct assignment, use FOR loop". This was due to a Salesforce limitation on querying large numbers of related records. :::: note ::: title ::: This issue impacted V14.1 and was identified in a known issue (KI-131). ::::The database queries have been optimized to directly fetch Contact Information records instead of Account records with their related Contact Information records, and field permissions on these objects have been updated. These changes resolve the query error as well as improve Account Search performance.
MIC-4069When users searched for an HCP on a new Interaction (Case) record, the Affiliation column did not appear in the Account Search results table.New Field (mvn__LY_Field__mdt), Layout Field (mvn__LY_Layout_Field__mdt), and Layout Section (mvn__LY_Layout_Section__mdt) metadata records have been added to ensure that the Affiliation column appears in the Account Search results table out of the box.
MIC-4074Users are allowed to add one new note on a closed Interaction (Case) record but should not be able to edit that note or add any additional notes. However, users were able to edit notes on recently closed interactions without any errors.Notes on closed interactions are no longer editable no matter when the interaction was closed, and an error message is thrown if a user attempts to edit a locked note.
MIC-4083If a user with the Run Ad Hoc QA (MED_Run_Ad_Hoc_QA) permission set did not have a default country, the user would run into the following error message in the Ad Hoc QA tab: "Argument cannot be null."Users with the Run Ad Hoc QA permission set can open and view the Ad Hoc QA page without errors, even if they do not have a default country set.
MIC-4084Documents of the Internal Document type and Work Instructions subtype should, but did not, appear in the documents list in the Work Instructions component. This was because the API names of the out-of-the-box picklist values on the Requester Type (MED_Requester_Type__c) field on the Interaction (Case) object and the Complainant Type (MED_Complainant_Type__c) field on the Product Quality Complaint (MED_Product_Quality_Complaint__c) object were incorrect.The API names of the out-of-the-box picklist values on the Requester Type and Complainant Type fields have been corrected, and documents appear in the Work Instructions component as expected.
PLTFM-2551When a user created a document without a file and then uploaded a rendition for the document, the document's metadata appeared in both the Preview and Details tabs on the Document record page. Additionally, in the Preview tab, the document's metadata appeared below the file preview and therefore overflowed outside the file preview component.If a document has a rendition, the Preview tab only shows the file preview and does not show the document's metadata. The document's metadata only appears in the Details tab.
PLTFM-2996When a workflow task was assigned to a user who already had the role that was required to complete the workflow task and then the workflow task was reassigned to another user, the role was taken from the original assignee and granted to the new assignee. This meant that the original assignee lost the role they already had. This also meant that the original assignee lost access to the document if that was their only role on the document.If a user is assigned a workflow task that grants them a role they already have and then another user is assigned the workflow task instead, the first assignee keeps their role on the document while the new assignee is also granted the role to complete the task.
PLTFM-3072Document roles could not be removed from users with open workflow tasks on documents, even if the document roles were not associated to the open tasks.Document roles can be removed from a user as long as the document roles are not associated to any of the user's open tasks on the document or the user is assigned the new CM Delete Document Role With Open Tasks (CM_Delete_Document_Role_With_Open_Tasks) custom permission.
PLTFM-3076The Request Translation button was always available in the Related Documents component, even if customers did not have the integrated language translation service. When users who did not have access to the translation service clicked the button, a wizard opened without any options.The Request Translation button is hidden from the Related Documents component of a document if the Enable Translation Requests (mvn__CM_Enable_Translation_Requests__c) field is disabled in the MCM Global Setting (mvn__CM_Global_Setting__mdt) custom metadata type.
PLTFM-3324NotIncludes was not a valid operator value in criteria definitions.Users can set the operator property to equal NotIncludes when creating criteria definitions.
custom-style="sorted-asc-type-text-col-1"}

Metadata changes​

The following subsections capture the changes against entities in key areas of that have been introduced in the latest release. This list is not exhaustive, as it does not contain changes that are internal to the application and that are not exposed to customers for customization, extension, or integration.

Custom labels​

Custom label changes are listed in the table(s) below:

New custom labels​
Work item(s)Custom label(s)
MIC-3923mvn__MED_Basic_Search mvn__MED_Record_Type mvn__MED_Restrict_Search
MIC-3987mvn__MED_Back
MIC-4000MED_Adverse_Event_Related_Record_Deleted_Message MED_Adverse_Event_Related_Record_Deleted_Success MED_Adverse_Event_Related_Record_Saved
PLTFM-3034, PLTFM-3037, PLTFM-3075, PLTFM-3096, PLTFM-3108, PLTFM-3109, PLTFM-3116, PLTFM-3127, PLTFM-3162, PLTFM-3193, PLTFM-3201mvn__CM_Authorize_File_Repository mvn__CM_Copy_Link mvn__CM_Create_Snapshot_Version mvn__CM_Document_New_Version_Snapshot_Email_Body mvn__CM_Document_New_Version_Snapshot_Feed_Body mvn__CM_Document_New_Version_Snapshot_Notification_Body mvn__CM_Document_Version_Snapshot_Log mvn__CM_External_File_Warning mvn__CM_File_Create_Type_Not_Supported mvn__CM_File_Repository_Auth_Close_Message mvn__CM_File_Repository_Auth_Close_Title mvn__CM_File_Repository_Back mvn__CM_File_Repository_Create mvn__CM_File_Repository_Create_New mvn__CM_File_Repository_Loading_More mvn__CM_File_Repository_New_Item mvn__CM_File_Repository_Select mvn__CM_Files_Connect mvn__CM_Files_Connect_Disclaimer mvn__CM_Files_Connect_Document mvn__CM_Files_Connect_Presentation mvn__CM_Files_Connect_Spreadsheet mvn__CM_Files_Connect_Upload_File mvn__CM_Latest_External_File_Warning mvn__CM_Latest_External_File_Warning_Header mvn__CM_Microsoft_Excel mvn__CM_Microsoft_PowerPoint mvn__CM_Microsoft_Word mvn__CM_Missing_File_Repository_Permissions mvn__CM_Missing_Files_Connect_File_Access mvn__CM_New_Snapshot_Version mvn__CM_No_Repositories mvn__CM_Open mvn__CM_Search_File_Repository mvn__CM_Select_From_File_Repository mvn__CM_Selected_File mvn__CM_Snapshot_Current_Version mvn__CM_System_Event_Document_New_Version_Snapshot
Modified custom labels​
Work item(s)Custom labelModification description
MIC-3968mvn__MED_Contact_Result_Column_Label_AddressThe value has been updated from Addresses to Address.
mvn__MED_Contact_Result_Column_Label_EmailThe value has been updated from Email Addresses to Email.
mvn__MED_Contact_Result_Column_Label_PhoneThe value has been updated from Phone Numbers to Phone.
mvn__MED_Parent_AccountsThe value has been updated from Parent Accounts to Affiliations.
MIC-4009MED_E2B_Generate_ButtonThe value has been updated from Generate to Yes. Submit AE.
MED_E2B_Generator_HeaderThe value has been updated from E2B(R3) Generator to Submit Adverse Event.
Custom metadata types​

Custom metadata type changes are listed in the tables below:

Note: New custom metadata records are only available via the - Setup plan in the .

New custom metadata type fields​
Work item(s)Custom metadata typeField
MIC-3975mvn__MED_Global_Setting__mdtmvn__MED_Account_Search_Excluded_Statuses__c
PLTFM-3034, PLTFM-3094, PLTFM-3116, PLTFM-3127mvn__CM_Global_Setting__mdtmvn__CM_Files_Connect_Excel_Template__c mvn__CM_Files_Connect_PowerPoint_Template__c mvn__CM_Files_Connect_Word_Template__c mvn__CM_Hide_External_File_Button__c mvn__CM_Hide_Files_Connect_File_Button__c mvn__CM_Hide_M365_File_Button__c mvn__CM_Hide_No_File_Button__c mvn__CM_Hide_Translation_File_Button__c mvn__CM_Hide_Upload_File_Button__c
custom-style="sorted-asc-type-text-col-4"}
New custom metadata records​
Work item(s)Custom metadata typeMetadata record name
MIC-3938mvn__LY_Field__mdtMED_Account_Source MED_Credentials MED_Primary_Language MED_Specialty
mvn__LY_Layout_Field__mdtMED_Secondary_Info_Account_Source_Inst MED_Secondary_Info_Account_Source_Person MED_Secondary_Info_Credentials_Inst MED_Secondary_Info_Credentials_Person MED_Secondary_Info_Primary_Lang_Inst MED_Secondary_Info_Primary_Lang_Person MED_Secondary_Info_Specialty_Institution MED_Secondary_Info_Specialty_Person
mvn__LY_Layout_Section__mdtMED_Account_Secondary_Results_Inst MED_Account_Secondary_Results_Person
MIC-4069mvn__LY_Field__mdtMED_Parent_Name
mvn__LY_Layout_Field__mdtMED_Search_Result_Parent
mvn__LY_Layout_Section__mdtMED_Results_Affiliation_Person
PLTFM-3034, PLTFM-3109mvn__SE_System_Event__mdtCM_Document_New_Version_Snapshot
mvn__SE_System_Event_Configuration__mdtCM_Document_New_Version_Snapshot
PLTFM-3034, PLTFM-3149mvn__CT_Content_Type__mdtbmp gif jpg png svg tiff zip
Modified custom metadata fields​
Work item(s)Custom metadata typeFieldModification description
PLTFM-3034, PLTFM-3109mvn__CM_Document_State_Entry_Action__mdtmvn__CM_Type__cThe New Snapshot Version (CM_New_Snapshot) picklist value will be available.
Objects​

Object changes are listed below.

New object fields​
Work item(s)ObjectField(s)
MIC-4008MED_AE_Drug_Information__cMED_E2B_Product__c MED_Other_Product__c MED_Related_Record_Label__c
MED_AE_Primary_Source__cMED_Related_Record_Label__c
PLTFM-3034, PLTFM-3168mvn__CM_Document__cmvn__CM_External_Content_Version_Id__c
PLTFM-3276mvn__CM_Document__cmvn__CM_Cloned_From__c
Modified object fields​
Work item(s)ObjectFieldModification description
MIC-4084CaseMED_Requester_Type__cThe API names of the out-of-the-box picklist values will have the MED_ prefix.
MED_Product_Quality_Complaint__cMED_Complainant_Type__c
Permissions​

Permission changes are listed in the table(s) below:

New permission sets​
Work item(s)Permission set
PLTFM-2931CM_ReassignTasks
New custom permissions​
Work itemCustom permission
MIC-4008MED_E2B_Submission
PLTFM-2931CM_Reassign_Task
PLTFM-3072CM_Delete_Document_Role_With_Open_Tasks
Modified permission sets​
Work itemPermission setModification description
MIC-4008MED_E2B_UserAdded the MED_E2B_Submission custom permission.
Static resources​

Static resource changes are listed in the table(s) below:

New static resources​
Work item(s)Static resource(s)
PLTFM-3034, PLTFM-3116cmExcelTemplate cmPowerPointTemplate cmWordTemplate
Validation rule​

Validation rule changes are listed in the table(s) below:

Note: New validation rules are only available via the - Setup plan in the .

New validation rules​
Work item(s)ObjectValidation rule
MIC-4008MED_AE_Drug_Information__cMED_Require_Product

Required pre-install & pre-upgrade actions​

This section includes the required actions administrators must take before installing and upgrading to the V16 release.

Enable Lightning Web Security​

Lightning Web Security (LWS) must be enabled to install and upgrade to the V16 release. For instructions, reference Salesforce's documentation on how to Enable Lightning Web Security in an Org.