Release notes
This topic contains the release notes for the Fall '25 release (or version 17) of Medical Information Cloud. Going forward, all major releases of the Medical Information Cloud product will be named after the season and year of their launch date to better align with Mavens's Medical Suite and Salesforce's releases.
The release notes are organized into these high-level sections:
New features – new features and functionalities to be introduced in the new release.
Updated features – existing features and functionalities to be enhanced in the new release.
Add-on packages with Mavens Labs – new optional packages that can be installed with the product.
Defect fixes and maintenance – defects and maintenance items to be fixed in the new version.
Metadata changes – changes to the underlying data models, user permissions, or system configurations to be included in the new version.
Deprecated and deleted items – components of the product that will be deprecated, removed, or retired in the new release.
Required pre-install & pre-upgrade actions – required actions that administrators must take before installing or upgrading to the new version.
Recommended post-upgrade actions – recommended actions administrators should take after upgrading to the new release.
As this page is maintained and updated over time to ensure accurate and timely information, Mavens recommends referencing the release notes online rather than printing and using static versions of the page. The Changelog page lists all notable changes made to this page.
For the release notes from earlier versions of Medical Information Cloud, visit the Archive.
New features
The Fall '25 release of Medical Information Cloud will contain several new features, the functionalities of which are detailed below. Details about enablement and configuration are included within the product documentation, which will be updated when the release is made available.
Branding update and enablement of SLDS 2
This past summer, we officially reintroduced ourselves as "Mavens". To both reflect the updated Mavens brand as well as incorporate Salesforce's new Lightning Design System 2 (SLDS 2), the upcoming release of the Medical Information Cloud product will include new colors, logos, and fonts. Customers are highly encouraged to upgrade to and enable SLDS 2 to ensure that the new Medical Information Cloud SLDS v2 (MedicalInformationCloudSLDSv2) theme appears as expected in the Medical Information Cloud product, including on the About Mavens Products page, in the MIC (Medical_Information_Cloud) app, and in the MIC - Administration (MIC_Administration_Lightning) app. The Medical Information Cloud SLDS v2 theme will automatically be enabled for new customers but will need to be manually activated for existing clients through the Themes and Branding page in Setup.
Related work item(s): MIC-4155, MIC-4187
Rich text fields for documents and emails
To enable users to add formatted content to documents and emails, such as for the fulfillment package emails in the new Digital Fulfillment feature below, a new Content (rich text) (mvn__CM_Content_Rich_Text__c) field will be available on the Document Version (mvn__CM_Document_Version__c) object. For documents without files, this rich text content can appear in place of the file in document previews. This is automatically enabled for new installs of the Medical Information Cloud product and can be manually enabled for upgrades when the Content (rich text) field is added to document layouts. For documents used in the fulfillment process, users must choose to either upload a file or use the Content (rich text) field but should not do both. For Cover Letter Component documents that are used by the Generate Package button on Fulfillment (MED_Fulfillment__c) record pages, users should upload a file that will be merged into the cover letter with the merged content or response document; for Cover Letter Component documents that are used by the new Digital Fulfillment button, users should use the Content (rich text) field to define the text that will build the email's message body.
Content inside rich text fields will be included in document searches, and all rich text fields will support merge fields which allow cross-object references. Additionally, rich text fields will now allow users to embed publicly available images that are either hosted in a Salesforce org and shared with a link or hosted on an external website; to ensure that images are properly included in emails, users should either insert the URL of the image or copy the image from the public location (e.g., right click on the image and select Copy) and then paste the image into the rich text field (e.g., right click in the field and select Paste).
Note
If you are upgrading to Fall '25 from a previous version of Medical Information Cloud, make sure to complete the steps in the Recommended post-upgrade actions section below to enable the new rich text fields in document preview and edit layouts.
Related work item(s): MIC-4123, MIC-4124, MIC-4127, MIC-4130, MIC-4145, MIC-4150, MIC-4190
Digital Fulfillment
To enhance the digital deliveries of fulfillment packages, Medical Information Cloud will introduce a new Digital Fulfillment feature in Fall '25 that offers a more configurable and flexible option for building dynamic email templates for an inquiry's fulfillment. To use this new feature, users will continue to first click the existing Generate Package (MED_Generate_Fulfillment_Package) button on Fulfillment (MED_Fulfillment__c) record pages to generate the fulfillment package and then click the new Digital Fulfillment (MED_Generate_Fulfillment_Letter) action to open the new email component. The email component will automatically include the fulfillment package and any other related files as separate attachments. It will also retrieve all of the applicable cover letter components and merge the text from the new Content (rich text) (mvn__CM_Content_Rich_Text__c) field mentioned in the Rich text fields for documents and emails section above as the email body. Merge fields in the cover letter component's rich text will automatically be replaced with the corresponding Fulfillment record values. The email's subject and from address can be configured by default or for each country. The email's recipients will default to the fulfillment's Email (MED_Email__c) and CC Email (MED_CC_Email__c) field values.
Users with the Customize Response on Fulfillment (MED_Customize_Response_on_Fulfillment) custom permission can modify the default or template values as desired, including changing the email subject, updating the dynamic email body, and reordering the attached files when previewing the email message. Users do not need the custom permission to modify the recipients.
Note
If you are upgrading to Fall '25 from a previous version of Medical Information Cloud, make sure to complete the steps in the Recommended post-upgrade actions section below to enable this new Digital Fulfillment feature.
Related work item(s): MIC-4127, MIC-4128, MIC-4143, MIC-4158, MIC-4194
Updated features
The Fall '25 release of Medical Information Cloud will also contain 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 will be shipped "off" by default for existing customers and "on" by default for new customers.
Upload multiple files to a request
In the new release, users will be able to upload multiple files to a Request (MED_Request__c) record through the MIC - Attach Request Document (medAttachRequestDocuments) component. After a user uploads one or more files to the component and clicks Done, the component will update to show the list of files that have been uploaded and will provide the user with the ability to upload more files as needed. Then, when the user clicks Submit, a Request Document (MED_Request_Document__c) record will be created and related to the Request record for each file that was uploaded. Any value that is set on any of the fields in the MIC - Attach Request Document modal will apply to all of the request documents that are created.
Related work item(s): MVN-86
Email notifications for replies to an interaction
The upcoming release will introduce a new Interaction: Reply Notification (MED_Interaction_Reply_Notification) autolaunched flow that is triggered on the Email Message (EmailMessage) standard object to notify Interaction (Case) record owners when there are incoming emails. In this way, when an inbound email is received for an interaction, the owner of the interaction can get a notification in their inbox alerting them of the new email. To send the notification, Medical Information Cloud uses the new MED_Interaction_Reply_Alert email alert, which sends the "New Interaction Email Notification" classic email template by default. Admin users can both configure the email alert to send a different template as well as modify the email template to send a different message.
Warning
This will only be available through the Medical Information Cloud - Setup configuration in the Install Service that is typically only used during new installations. If you are upgrading to Fall '25 from a previous version of Medical Information Cloud, please reach out to your client partner.
Related work item(s): MIC-2405
Files included in request snapshots
In the new release, snapshots that are created for Request (MED_Request__c) records using the Nintex integration will include a table of the Request Document (MED_Request_Document__c) records related to the request. This will provide more detail on what content was used to respond to each request.
Warning
This will only apply to new installations. If you are upgrading to Fall '25 from a previous version of Medical Information Cloud and would like to have this new functionality, please reach out to your client partner or your client delivery lead.
Related work item(s): MIC-2637
Add Quick Search to any record page with Case lookup
The MIC - Case Accounts Quick Search (mvn.medCaseAccountsQuickSearch) component, otherwise known as simply the Quick Search component or Account Search, can be added to any object's Lightning Record Page as long as that object has a relationship with the Interaction (Case) object. Admin users must set the new Case Lookup Field API Name field on the component in order to retrieve data from the correct Interaction record.
Related work item(s): MIC-3971
Rename files in the MIC - Fulfillments Files List component
The MIC - Fulfillments Files List (medFulfillmentAttachments) Lightning component will be updated to let users with the Customize Response on Fulfillment (MED_Customize_Response_on_Fulfillment) custom permission more easily rename files on Fulfillment (MED_Fulfillment__c) record pages. To rename a file, users can click the down arrow at the far right end of the row in the component and then select Rename. The Rename File modal will then open where users can enter a new file name and click Rename. Admin users can change the modal title and the button label with the MED_Rename_Title and MED_Rename_Button custom labels, respectively.
Related work item(s): MIC-4125
E2B updates and fixes
Several updates will be made to the E2B functionality in the upcoming Fall '25 release.
Warning
These updates are optional and will be available through the Install Service in both the Medical Information Cloud configuration and the Medical Information Cloud - E2B configuration. You can therefore install these updates either during the typical upgrade or installation process by checking the Install Package mic-e2b step in the Medical Information Cloud configuration or any time after the Fall '25 release using the Medical Information Cloud - E2B configuration.
Sender information and telecom tag prefix
Currently, E2B files do not include the sender's phone number (C.3.4.6), fax number (C.3.4.7), or email address (C.3.4.8) and only contain the raw value of the reporter's phone number (C.2.r.2.7). In the upcoming release, the sender's telecommunication information will be added to E2B files and the <telecom> tag for every reporter and sender's phone number, sender's fax number, and sender's email address will be prefixed with tel:, fax:, and mailto:, respectively, as long as a prefix does not already exist. To enable this, a new Sender's Fax (MED_Sender_Fax__c) field on the E2B Setting (MED_E2B_Setting__mdt) custom metadata type will also be introduced.
Related work item(s): MIC-3861
Set MedDRA version globally
If MedDRA is used with E2B, admin users are required to set the value of the MedDRA version to be used throughout the generated E2B file, such as on the MedDRA Version for Medical History (D.7.1.r.1a) element, the MedDRA Version for Indication (G.k.7.r.2a) element, and more. Currently, this is a manual process, and the MedDRA version is the same for every element. In the upcoming release, admin users can just set the MedDRA version value once on the new MedDRA Version (MED_MedDRA_Version__c) field on the E2B Setting (MED_E2B_Setting__mdt) custom metadata type so that it can be used for every MedDRA-related element across all E2B files. Existing MedDRA version fields on the AE Drug (MED_AE_Drug_Information__c), AE Drug History (MED_AE_Drug_History__c), AE Medical History (MED_AE_Medical_History__c), and AE Test Result (MED_AE_Results__c) objects will be deprecated accordingly.
Related work item(s): MIC-3909
Include D.10.7.1.r.4 and G.k.4.r.5 independent of D.10.7.1.r.2, G.k.4.r.4, and G.k.8
Currently, E2B files may omit the (Medical History) End Date (D.10.7.1.r.4) element when the (Medical History) Start Date (D.10.7.1.r.2) element is empty and may omit the Date and Time of Last Administration (G.k.4.r.5) element when the Date and Time of Start of Drug (G.k.4.r.4) element is empty or when the Action(s) Taken with Drug (G.k.8) element is populated. Based on client feedback, generated E2B files in the upcoming release will include D.10.7.1.r.4 even if D.10.7.1.r.2 is not set and will include G.k.4.r.5 regardless of whether G.k.4.r.4 and G.k.8 are also included.
Related work item(s): MIC-4131, MIC-4135
Annotate files with the enhanced document viewer
Users will be able to provide annotations on Word and PDF files when previewing documents with the enhanced document viewer in Regulated Content Cloud. To enable the new annotating functionality, admin users must first activate the File Annotations (WV_File_Annotations) Feature Activation (mvn__Feature_Activation__mdt) metadata record and then create a custom Document State Role Permission (mvn__CM_Document_State_Role_Permission__mdt) metadata record that looks up to the new Annotate (CM_Annotate) Permission (mvn__CM_Permission__mdt) metadata record. Users without the appropriate permission will only be able to view annotations. Additionally, annotations are not supported for video files or files that are part of a bundle package. All annotations will be stored in the new File Marker (mvn__WV_File_Marker__b) big object.
Related work item(s): PLTFM-3429
Add-on packages with Mavens Labs
Mavens Labs is a new program where Mavens engineers, professional services staff, and other employees share modules and apps that they have created through inspiration and collaboration with the client community. These modules and apps are not official products and should be considered as community projects that can be installed separately through the Install Service. They are not officially validated or documented, and updates may be available outside of the typical release cycle. As a result, they are provided "as is," are not supported by Mavens's product teams, and may be used by clients at their own risk. Additional licensing may apply. Please reach out to your client partner for more information.
Artificial Intelligence in Medical Information (AIMI)
To facilitate processes within Medical Information, Mavens Labs will begin to offer optional packages that utilize or augment Salesforce's Agentforce AI platform. These add-on packages are collectively referred to as Artificial Intelligence in Medical Information (AIMI) and complement the Medical Information Cloud product by providing prompt templates specific to medical information, prompt flows for secure data retrieval within the product, as well as a new AIMI Prompt Selection modal that offers a procedurally driven UI for a "governed agentic AI" approach. This approach ensures that there remains a human in the loop with all of the enhanced automations and enables Medical Information specialists to have complete control over the additional efficiencies in interaction management. In doing so, AIMI provides these Medical Information specialists with recommendations, summaries, and general assistance that can improve the overall performance, quality, and delivery of their current work.
All of AIMI's capabilities and tools are optional, configurable, templated, and secure. They build on top of Salesforce's Agentforce, Einstein, and Data 360 platforms and, as such, have an immutable paper trail, secure data retrieval, and zero data retention to ensure that no client information is stored outside of client's systems.
To use AIMI with the Medical Information Cloud product, admin users must activate each out-of-the-box prompt template and prompt flow they wish to use. While the templates provided are specific to Medical Information services, Mavens strongly encourages teams to revise the templates to better meet specific business needs.
Admin users can also add the AIMI Prompt Component to the Interaction Lightning Record Page as desired for users to use the AIMI Prompt Selection modal. The modal retrieves AIMI Prompt Option (MAI_AIMI_Prompt_Option__mdt) custom metadata records, so admins can define which prompt templates to show to users, if the prompts should run by default or not, and what corresponding flow should take a user's response to perform an action.
Warning
Customers must purchase their own Agentforce licenses to install and use AIMI.
Related work item(s): MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196
Defect fixes and maintenance
Table 5, “Fixed items” details defects and maintenance items identified in V16 that will be fixed in the Fall '25 release.
Work item | Description | New behavior |
|---|---|---|
MIC-3482 | AuraHandlerException, the Apex exception class required to throw errors for Aura components, obscures errors in Lightning Web Components (LWCs). This causes "Script-thrown exception" to be the only error message to appear for LWC errors, which could be vague and confusing for users. | AuraHandlerException will be removed for LWCs so that users can see more relevant and informative error messages for errors in LWCs. New custom labels will also be available for translating error messages. |
MIC-3961 | When a user selects a value in a picklist field of the New Account modal and then immediately tries to change their selection, the field does not re-open with the list of values. Instead, the user must first click out of the picklist field (i.e., anywhere else in the New Account modal) and then click on the field again for the values to appear. | The New Account modal will be updated so that users can click on any picklist field to open its list of values, select an option, and then immediately click on the same picklist field again to re-open the list of values. Users will no longer have to first click somewhere else in the New Account modal to change their selection in a picklist field. |
MIC-4104 | When a product is stamped on the Product ( | If the Product field on a Request record is populated with a value that does not meet the lookup field's filter criteria such that no matching Product ( |
MIC-4158, MIC-4193 | The Configure Fulfillment Package modal throws the following error message using the MED_Fulfillment_Error_No_Documents custom label when there are no relevant cover letter components for the Fulfillment ( | The Configure Fulfillment Package modal will only throw an error when a user clicks Run in the modal and there are both no relevant cover letter components for the fulfillment and no files on the Request Document record whose Delivery Option ( |
MIC-4166 | When the anonymization batch job is run and a related file is linked to multiple Request ( | File IDs will be deduplicated before files and documents are deleted so that the anonymization batch job no longer throws the error. |
MIC-4169 | When auto save and manual save are both enabled on the MIC - Enhanced Record Edit ( | When users click the Save button in the component to manually save changes, the autosave criteria will reset so as to not trigger an additional save unexpectedly. |
MIC-4211 | Users are sometimes able to edit existing notes on closed Interaction ( NoteThis issue was previously acknowledged and partially addressed by MIC-4074 in V16. | All existing notes on closed interactions will be locked and will not be editable. If a user tries to edit an existing note on a closed interaction, an error will be thrown. |
MIC-4212 | Account Search V3 throws an error when non-admin users try to create a new account on an interaction because the users do not have access to the non-global LY_LayoutController Apex class. | The Medical Information Cloud Admin ( |
PLTFM-3097 | In the Upload New Version modal in Regulated Content Cloud, users are able to create a new version of a document without uploading a file. | The Upload New Version modal will require a file to be uploaded for every new document version. If users click Save without uploading a file, an error message will appear. |
PLTFM-3556 | The Apex classes and triggers in Medical Information Cloud are currently on older and different versions of Salesforce's API. | All of the Apex classes and triggers in Medical Information Cloud will be updated to Salesforce's latest API version, Version 64.0, to have the latest platform features, performance improvements, and security enhancements. |
Metadata changes
The following subsections capture the changes against entities in key areas of Medical Information Cloud that will be introduced in the latest release. This list is not exhaustive, as it only contains changes to metadata and entities that are exposed to system administrators for customization, extension, and/or integration.
Custom label changes are listed in the table(s) below:
Work item(s) | Custom label(s) |
|---|---|
MIC-3482 | MED_Fieldset_Not_Found MED_Layout_Not_Found |
MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196 | MAI_AIMI_Prompt_Selection MAI_AIMI_Response MAI_Ask_AIMI MAI_Back MAI_Cancel MAI_Detect_AE MAI_Detect_AE_Description MAI_Detect_PQC MAI_Detect_PQC_Description MAI_Run |
MIC-4104 | MED_Search_Products_Unmatched MED_Search_Products_Unmatched_Error |
MIC-4125 | MED_Rename_Button MED_Rename_Title |
MIC-4127, MIC-4128, MIC-4143, MIC-4158, MIC-4193, MIC-4194 | EM_Attachments EM_BCC EM_CC EM_Email_Template EM_From EM_Related_Record EM_Subject EM_To MED_Email_Fulfillment_Title MED_Email_Remove_Attachment_Confirm MED_Email_Send_Success MED_Fulfillment_Email_Subject MED_Fulfillment_Section_Letterhead MED_Generating_Email_Body MED_Merge MED_Package_Job_No_Files_Error |
PLTFM-3097 | CM_Document_Version_No_File_Message |
PLTFM-3169, PLTFM-3170, PLTFM-3172, PLTFM-3173, PLTFM-3185, PLTFM-3300, PLTFM-3303 | CM_Add_File_No_Options_Instructions CM_Authorize_File_External_Service CM_Can_Not_Replace_Existing_File CM_Document_Version_Can_Not_Replace_File CM_Document_Version_No_Folder_Message CM_File_External_Auth_Close_Message CM_File_No_Options CM_File_Repository_Select_File CM_File_Repository_Select_Folder CM_File_Size_Limit_Exceeded CM_New_External_Version CM_Package_File_Queue_Success_Message CM_Replace_Existing_File CM_Replace_File CM_Selected_Folder CM_Service_File_Size_Limit_Exceeded CM_Snapshot_File_Size_Limit_Exceeded CM_Snapshot_Queue_Success_Message CM_Upload_External_Version CM_Upload_New_File |
PLTFM-3429 | CM_permission_annotate WV_Mention_Notification_Body WV_Mention_Notification_Title WV_Unsupported_File_Type |
Work item(s) | Custom label | Modification description |
|---|---|---|
PLTFM-3169, PLTFM-3170, PLTFM-3172, PLTFM-3173, PLTFM-3185, PLTFM-3300, PLTFM-3303 | CM_Add_File_Instructions | Value was updated from |
Custom metadata type changes are listed in the table(s) below:
Table 10, “New custom metadata records”
Note
New custom metadata records are only available via the Medical Information Cloud - Setup configuration in the Install Service that is typically only used for new installations.
Work item(s) | Custom metadata type |
|---|---|
MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196 | MAI_AIMI_Prompt_Option__mdt |
PLTFM-3429 | mvn__Feature_Activation__mdt |
Work item(s) | Custom metadata type | Field(s) |
|---|---|---|
MIC-3861 | MED_E2B_Setting__mdt | MED_Sender_Fax__c |
MIC-3909 | MED_E2B_Setting__mdt | MED_MedDRA_Version__c |
MIC-4158 | MED_Local_Setting__mdt | MED_Fulfillment_Email_Subject_Label__c MED_Fulfillment_Outbound_Email__c |
PLTFM-3169, PLTFM-3170, PLTFM-3172, PLTFM-3173, PLTFM-3185, PLTFM-3300, PLTFM-3303 | mvn__CM_Global_Setting__mdt | mvn__CM_Enable_External_Files_Connect__c mvn__CM_Files_Connect_Environment__c mvn__CM_Files_Connect_Snapshot_To_Current__c |
Work item(s) | Custom metadata type(s) | Metadata record name(s) |
|---|---|---|
MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196 | MAI_AIMI_Prompt_Option__mdt | MED_Detect_Adverse_Event MED_Detect_PQC |
MIC-4123, MIC-4124, MIC-4127, MIC,4130, MIC-4145, MIC-4150, MIC-4190 | mvn__LY_Field__mdt | CM_Context_Rich_Text |
mvn__LY_Layout_Field__mdt | CM_Document_Detail_CL_Rich CM_Document_Detail_CR_Rich CM_Document_Detail_Default_Rich CM_Document_Detail_FAQ_Rich CM_Document_Detail_Internal_Rich CM_Document_Detail_Medical_Rich CM_Document_Detail_RD_Rich CM_Document_Detail_WI_Rich CM_Document_Edit_CL_Rich CM_Document_Edit_CR_Rich CM_Document_Edit_Default_Rich CM_Document_Edit_FAQ_Rich CM_Document_Edit_Internal_Rich CM_Document_Edit_Medical_Rich CM_Document_Edit_RD_Rich CM_Document_Edit_WI_Rich CM_Document_Preview_Default_Rich CM_Document_Preview_FAQ_Rich CM_Wizard_Confirm_CL_Rich CM_Wizard_Confirm_CR_Rich CM_Wizard_Confirm_Default_Rich CM_Wizard_Confirm_FAQ_Rich CM_Wizard_Confirm_Internal_Rich CM_Wizard_Confirm_Medical_Rich CM_Wizard_Confirm_RD_Rich CM_Wizard_Confirm_WI_Rich CM_Wizard_Detail_CL_Rich CM_Wizard_Detail_CR_Rich CM_Wizard_Detail_Default_Rich CM_Wizard_Detail_FAQ_Rich CM_Wizard_Detail_Internal_Rich CM_Wizard_Detail_Medical_Rich CM_Wizard_Detail_RD_Rich CM_Wizard_Detail_WI_Rich | |
MIC-4127, MIC-4128, MIC-4143, MIC-4158, MIC-4194 | mvn__LY_Layout_Field__mdt | CM_Document_Detail_CL_Delivery CM_Document_Edit_CL_Delivery CM_Document_Preview_Default_Delivery CM_Wizard_Confirm_CL_Delivery CM_Wizard_Detail_CL_Delivery |
MIC-4193 | MED_Dynamic_Fulfillment_Setting__mdt | CM_Letterhead |
PLTFM-3429 | mvn__CM_Permission__mdt | CM_Annotate |
Flow changes are listed in the table(s) below:
Work item(s) | Flow(s) |
|---|---|
MIC-2405 | MED_Interaction_Reply_Notification |
MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196 | MAI_Interaction_Get_Available_Products MAI_Interaction_Get_Content_Notes MAI_Interaction_Get_Email_Content MAI_Interaction_Get_Request_Details MAI_Request_Get_Available_Categories |
Lightning action changes are listed in the table(s) below:
Work item(s) | Object | Lightning action |
|---|---|---|
MIC-4127, MIC-4128, MIC-4143, MIC-4158, MIC-4194 | MED_Fulfillment__c | MED_Generate_Fulfillment_Letter |
Lightning Web Component changes are listed in the table(s) below:
Work item(s) | Lightning Web Component(s) |
|---|---|
MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196 | maiAimiPromptComponent |
MIC-4127, MIC-4128, MIC-4143, MIC-4158, MIC-4194 | MED_Generate_Fulfillment_Letter medGenerateFulfillmentLetter |
Object changes are listed in the table(s) below:
Work item(s) | Object |
|---|---|
PLTFM-3429 | mvn__WV_File_Marker__b |
Work item(s) | Object | Field(s) |
|---|---|---|
MIC-4123, MIC-4124, MIC-4127, MIC-4130, MIC-4145, MIC-4150, MIC-4190 | mvn__CM_Document_Version__c | mvn__CM_Content_Rich_Text__c |
MED_Request_Document__c | MED_Rich_Text_Content__c |
Work item(s) | Object | Field | Modification description |
|---|---|---|---|
MIC-4127, MIC-4128, MIC-4143, MIC-4158, MIC-4194 | mvn__CM_Document_Version__c | mvn__CM_Delivery_Option__c | Added |
MED_Request_Document__c | MED_Delivery_Option__c | Added | |
MED_Mock_Delivery_Option__c | Added | ||
PLTFM-3169, PLTFM-3170, PLTFM-3172, PLTFM-3173, PLTFM-3185, PLTFM-3300, PLTFM-3303 | mvn__CM_Document_Version__c | mvn__CM_Check_Out_Type__c | Added |
Work item | Object(s) | Field(s) |
|---|---|---|
MIC-3909 | MED_AE_Drug_History__c | MED_MedDRA_Version_for_Indication__c MED_MedDRA_Version_for_Reaction__c |
MED_AE_Drug_Information__c | MED_MedDRA_Version_for_Indication__c | |
MED_AE_Medical_History__c | MED_MedDRA_Version_for_Medical_History__c | |
MED_AE_Results__c | MED_MeDRA_Version_for_Test_Name__c |
Prompt template changes are listed in the table(s) below:
Work item(s) | Prompt template(s) |
|---|---|
MIC-4015, MIC-4031, MIC-4113, MIC-4114, MIC-4115, MIC-4188, MIC-4193, MIC-4196 | MAI_Interaction_AE_Recommendation MAI_Interaction_Product_And_Question MAI_Interaction_Product_Complaint_Recommendation MAI_Interaction_Summary MAI_Request_Suggest_Category |
Deprecated and deleted items
The following entities will be either deprecated or deleted from the latest release of Medical Information Cloud and will no longer be available or supported in future releases.
Work item | Object(s) | Field(s) |
|---|---|---|
MIC-3909 | MED_AE_Drug_History__c | MED_MedDRA_Version_for_Indication__c MED_MedDRA_Version_for_Reaction__c |
MED_AE_Drug_Information__c | MED_MedDRA_Version_for_Indication__c | |
MED_AE_Medical_History__c | MED_MedDRA_Version_for_Medical_History__c | |
MED_AE_Results__c | MED_MeDRA_Version_for_Test_Name__c |
Required pre-install & pre-upgrade actions
This section includes the required actions administrators must take before installing and upgrading to the Medical Information Cloud Fall '25 release.
Enable Lightning Web Security
Lightning Web Security (LWS) must be enabled to install and upgrade to the Medical Information Cloud Fall '25 release. For instructions, reference Salesforce's documentation on how to Enable Lightning Web Security in an Org.
Recommended post-upgrade actions
This section includes the recommended actions administrators should take after upgrading to Medical Information Cloud Fall '25 to enable the new features and enhancements. Each action specifies the criteria for consideration, which details the conditions that must exist to warrant action by a customer.
Enable rich text fields for documents and emails
If you are upgrading from a previous version of Medical Information Cloud to Fall '25 and would like to enable Rich text fields for documents and emails, you must add the Content (rich text) (mvn__CM_Content_Rich_Text__c) field to preview and edit layouts. To do so:
Create a new Field (
mvn__LY_Field__mdt) metadata record with the following values:Label
Content (rich text)
SObject
mvn__CM_Document_Version__c
Field API Name
mvn__CM_Content_Rich_Text__c
Create a new Layout Field (
mvn__LY_Layout_Field__mdt) metadata record for each existing Layout Type (mvn__LY_Layout_Type__mdt) metadata record that should now include the new field from step 1. Mavens recommends creating a Layout Field metadata record for edit layouts so that users can add and modify the rich text content as well as for document preview layouts so that the rich text content can appear in place of a nonexistent file for documents without files. You may reference Table 10, “New custom metadata records” above for the list of Layout Field metadata records you may wish to create.
Enable Digital Fulfillment
If you are upgrading from a previous version of Medical Information Cloud to Fall '25 and would like to enable the new Digital Fulfillment feature, you must complete the following actions:
Note
The Digital Fulfillment process is an optional feature that can be used with the traditional fulfillment package generation process. These steps therefore do not impact the current functionality of the Generate Package button on Fulfillment (MED_Fulfillment__c) record pages.
Add HTML Only value to Delivery Option picklist fields
To add the HTML Only value to the Delivery Option picklist field on the Document Version object:
Open the Document Version (
mvn__CM_Document_Version__c) object in the Object Manager.On the Delivery Option (
mvn__CM_Delivery_Option__c) field, addHTML Onlyas a new picklist value.
To add the HTML Only value to the Delivery Option picklist fields on the Request Document object:
Open the Request Document (
MED_Request_Document__c) object in the Object Manager.On the Delivery Option (
MED_Delivery_Option__c) field, addHTML Onlyas a new picklist value.On the Mock Delivery Option (
MED_Mock_Delivery_Option__c) field, addHTML Onlyas a new picklist value.
Add Delivery Option field to cover letter layouts
To add the Delivery Option field to the Document Detail - Cover Letter layout, create a new Layout Field (
mvn__LY_Layout_Field__mdt) metadata record with the following values:Label
Document Detail CL - Delivery Option
Layout Type
Document Detail - Cover Letter (
CM_Document_Detail_Cover_Letter)Field
Delivery Option (
CM_Delivery_Option__c)To add the Delivery Option field to the Document Edit - Cover Letter layout, create a new Layout Field (
mvn__LY_Layout_Field__mdt) metadata record with the following values:Label
Document Edit CL - Delivery Option
Layout Type
Document Edit - Cover Letter (
CM_Document_Edit_Cover_Letter)Field
Delivery Option (
CM_Delivery_Option__c)To add the Delivery Option field to the Document Preview Default layout, create a new Layout Field (
mvn__LY_Layout_Field__mdt) metadata record with the following values:Label
Document Preview Default - Delivery
Layout Type
Document Preview Default (
CM_Document_Preview_Default)Field
Delivery Option (
CM_Delivery_Option__c)To add the Delivery Option field to the Doc Wizard Confirm - Cover Letter layout, create a new Layout Field (
mvn__LY_Layout_Field__mdt) metadata record with the following values:Label
Wizard Confirm CL - Delivery Option
Layout Type
Doc Wizard Confirm - Cover Letter (
CM_Doc_Wizard_Confirm_Cover_Letter)Field
Delivery Option (
CM_Delivery_Option__c)To add the Delivery Option field to the Doc Wizard Detail - Cover Letter layout, create a new Layout Field (
mvn__LY_Layout_Field__mdt) metadata record with the following values:Label
Wizard Detail CL - Delivery Option
Layout Type
Doc Wizard Detail - Cover Letter (
CM_Doc_Wizard_Detail_Cover_Letter)Field
Delivery Option (
CM_Delivery_Option__c)
Create new cover letter components with HTML Only delivery option and rich text content
To create cover letter components that can be used by the Digital Fulfillment button that will be enabled in the Add Digital Fulfillment action to Fulfillment page layout step below, create a new document in Regulated Content Cloud and:
Set the Delivery Option (
mvn__CM_Delivery_Option__c) field toHTML Only.Add content to the Content (rich text) (
mvn__CM_Content_Rich_Text__c) field.
The rich text will then be merged as HTML into the email body to create a dynamic email template.
Note
The Digital Fulfillment button and the Generate Package button can be used together, but users must not upload a file and use rich text on the same cover letter component.
To continue to create cover letter components that can be used when generating the fulfillment package, create a new cover letter component in Regulated Content Cloud and upload a file to the document, as in previous versions of Medical Information Cloud.
Add Digital Fulfillment action to Fulfillment page layout
To add the Digital Fulfillment (MED_Generate_Fulfillment_Letter) action to the Fulfillment page layout:
Open the Fulfillment page layout in the Lightning App Builder.
Click on the Highlights Panel to edit it and click Add Action.
Search for and select Digital Fulfillment.
Click Done.
Drag and drop the Digital Fulfillment action in the Actions list to position it as desired. For example, move it right under the Generate Package quick action.
Click Save.