V12 release notes

MIC-2964

When a user tries to check out a response letter from a list of files, the wrong document is checked out. Instead of the selected document, the last document in the Fulfillment Files list is checked out instead. This issue was identified by users after they upgraded their dev org to V12.

The correct document is now checked out when selected by the user.

V12.0.1

V12

MIC-2990

Some account external IDs could cause Inbound form processing to fail with an InstanceOf ID error.

External IDs no longer result in inbound forms failing.

V12.0.2

V12

MIC-2974/MIC-3013

When using the new Account Search V3 subsystem, Request creation for MIRFs may sometimes fail with the following error found in the Debug Logs object: System.TypeException: Invalid id value for this SObject type: 243209199570387973. This is because the Salesforce Apex call instanceof Id has a bug where it does not do a proper check on whether the string is a valid SObject Id.

Request creation for MIRFs no longer fails for Requester_External_ID, specifically.

V12.0.2

V12

MIC-3268/MIC-3296

Previously, users could not modify another user's notes. However, in the V12 release, this ability was inadvertently turned on for new notes (not existing notes), thereby allowing users to modify one another's notes.

The V12.0.4 hotfix reversed this change so that users are once again not allowed to edit each other's notes.

V12.0.4

V12, V13

MIC-142

After escalation, finalizing the fulfillment package does not delete the previous document. Document duplication can occur across a variety of use cases, particularly if the user running the finalization process was not the user who generated the package initially. Only the latest version is attached to the record.

Package-generated documents will now be replaced, instead of duplicated when uploading a new version.

MIC-206

An INVALID_TYPE_ON_FIELD_IN_RECORD error occurred if a document was selected that had an unpopulated field NULL value mapped to Veeva Vault's Yes/No field type. This issue was detailed in Known Issue 48 (KI-48).

Now, the Vault Search Handler (MED_VaultSearchHdlr) will skip assigning a value to that field on the document record, which will prevent the error.

MIC-233

If a Vault field contained a multi-select picklist, the MED_VaultSearchHdlr was only retrieving the first value, instead of all.

When searching for content in Veeva Network, results will now accurately match against Veeva fields of the multi-select picklist type.

MIC-695

When creating a Fulfillment for an Interaction after the requester has been changed from one HCP to an HCP that does not have contact information, the contact information from the first HCP is retained and populates the Fulfillment information fields.

Now, when an Interaction's associated requester is changed, the stamped account details will clear if the new requester does not have corresponding contact information records.

MIC-2272

The autosearch process was firing before the Content Search form was fully rendered. This caused any default fields with default values to appear empty.

The MED_ContentSearchCtrl Apex class was updated so that Default values are now honored when conducting initial Content searches.

MIC-2537

If the Interaction lookup is not on the Adverse Event (AE) or Product Quality Complaint (PQC) page layouts, the AE drug never gets created and the modal does not close. Additionally, if the Request product is blank, completing that field does not create the AE drug. This issue was addressed in Known Issue 66 (KI-66).

These issues were corrected by making the Interaction lookup no longer a requirement on the AE/PQC page layouts.

MIC-2547

The Add Related Adverse Event and Add Related Product Quality Complaint components were only copying to/from the MED_Question_Rich__c field, which didn't work properly for customers using V10.

A new method was added to the medStringUtil that will format rich text strings as plain text fields. Additionally, the previous MED_Question__c value will now be appended to the Narrative/Complaint if there is data.

MIC-2568

The text/value of the MED_Answer__c field was not formatted correctly when copied to the Request Document (MED_Request_Document__c) object. This error occurred regardless of what field it was mapped to.

The rich text in the MED_Answer__c field is now only removed when copying it to the plain text MED_Request_Document__c object.

MIC-2572

Documents with bundled relationships were not included on requests if a related document was selected. This issue was detailed in Known Issue 68 (KI-68).

The API name referenced in the MED_ContentSearchHdlr class was updated from Bundle to CM_Bundle. This corrected the problem.

MIC-2573

Email attachments were not handled correctly by the custom Email Handler (MED_InboundEmailHandler) because the IsClientManaged flag was not set to true for attachments.

Inbound Email-to-Case messages that have attachments will now show those attachments on the case file related list if "Show Email Attachments in Case Attachments Related List" is set to true in Support Settings.

MIC-2574

When an Adverse Event or Product Quality Complaint was created, changes made to the product selection were not honored.

The source data is prevented from reloading and overwriting product selection. The selected product is now honored.

MIC-2579

Insufficient padding was noted between the Search Content field and the barrier of the Request Content Search component. This issue was detailed in Known Issue 76 (KI-76).

This was a cosmetic issue that was fixed by adding a padding class to the search box input.

MIC-2591

Running batch or ad hoc QA processes on new Interaction QA objects will prompt an error message if the Interaction objects have a QA status of N/A. This is because N/A, which was the default value for the QA status before V9, is a valid picklist value on Interaction objects but not on the new QA objects. This issue is detailed in Known Issue 69 (KI-69).

A background utility now checks for incoming invalid N/A statuses when creating new Interaction QA records. When an invalid status is found, the system will change the status to "Review Required".

MIC-2496

Users received an error when attempting to attach a Vault document to a request that was bigger than 2147483647 (max size of a 32-bit signed integer). This was because the value of the size__v field was in memory as a generic Object, resulting in the error because the number was too large.

This was resolved by casting the incoming numerical values as either Integer or Decimal based on the field type and then adding them to the mapping. This removed the overflow error for that field since Integer and Decimal have much higher max values than Object.

MIC-2623

Inbound email messages were "bouncing" back (i.e., not delivering) if the content was too large.

Inbound email messages will now be truncated (if needed), and the full, raw message will be attached to the email as a TXT file, thereby preventing large messages from bouncing.

MIC-2636

The Date of Awareness in an AE/PQC did not accurately reflect the current user's timezone and instead defaulted to UTC or the org default timezone.

To correct this, the C.1.5 E2B element was made a configurable record in the E2B Field Mapping (MED_E2B_Field_Mapping__mdt) custom metadata type.

MIC-2653

When adding a new related AE or PQC to an Interaction, the date field was stamped with the local computer's timezone.

The user's Salesforce timezone is now stamped on the related AE/PQC.

MIC-2684

In a few instances, the fulfillment utility bar would fail when processing non-JSON messages from non-MIC sources, triggering a pop-up message. This issue was detailed in Known Issue 83 (KI-83).

The code has been updated so that it will catch parsing errors and ignore messages not meant for it.

MIC-2686

The MED_FulfillmentCloseCleanup Apex class was not processing Fulfillments correctly when the Fulfillment's status was changed to "Cancelled".

To resolve this, the MED_FulfillmentCloseCleanup Apex class was refactored to differentiate between "Completed" (Fulfilled) and "Closed" (either Fulfilled or Cancelled) so that the related Fulfillment objects process accordingly.

MIC-2699

When document usage reporting is enabled and a document from Medical Information Cloud Content Management is used in a Request, the document usage should be logged in the Document record’s audit log. However, two document usages instead of one are logged. This is because field updates in the Request workflows edit the Request record twice. This issue was detailed in Known Issue 80 (KI-80).

A "run once check on request" trigger (MED_ContentRequestReportHdlr.firstRun) was added the to content-core default trigger logic to prevent the error in log handling.

MIC-2746

The Country was not stamped on Request Documents for results from Medical Information Cloud Content Management.

The Country is now stamped on Medical Information Cloud Content Management Request Documents.

MIC-2755

Product names did not appear on the Request Document attachment list.

Product names are now displayed correctly.

MIC-2823

A mismatch in the default metadata record of the Language (CM_Language __c) field in the Document Version (mvn__CM_Document_Version__c) custom object was causing an issue that prevented the creation of an attachment.

The default metadata record has been updated to correct this issue.

MED_WorkspaceRefresh

This component has been deprecated.

Mavens Key Contact

Deprecated