Release notes

MIC-2753

The 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-3905

When 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-3911

The 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-3918

When 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.

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-4069

When 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-4074

Users 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 be editable no matter when the interaction was closed, and an error message is thrown if a user attempts to edit a locked note.

MIC-4083

If 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-4084

Documents 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-2551

When 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-2996

When 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-3072

Document 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-3076

The 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-3123

When a workflow was started and tasks were assigned to multiple users, every user received notifications about the task assignments, including the tasks that were assigned to other users.

Users will only be notified about tasks that are assigned to themselves. Notifications are no longer sent for tasks that are assigned to other users.

PLTFM-3324

NotIncludes was not a valid operator value in criteria definitions.

Users can set the operator property to equal NotIncludes when creating criteria definitions.