V15 release notes
This topic contains release notes for V15 of . The release notes are organized into these high-level sections:
-
New features - new features and functionalities released in version 15.
-
Updated features - updated features and functionalities released in version 15.
-
Additional enhancements - provides information on additional enhancements made in version 15.
-
Defect fixes and maintenance - fixed defects and maintenance items within the new release.
-
Metadata changes - changes to the underlying data models, user permissions, or system configurations included within the new release.
-
Post-upgrade required actions -- required actions administrators must take after upgrading to the new version of .
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.
New features
The V15 release of contains 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.
Manage expiring and expired documents checked out to Microsoft 365
Documents checked out to Microsoft 365 for 180 days or more become
"expired" and are no longer accessible. To help users better track and
manage Document Version (mvn__CM_Document_Version__c) records that are
checked out to Microsoft 365, now provides
CM_CheckOutExpirationSchedulable and
CM_CancelExpiredCheckedOutDocumentsBatch as two new schedulable jobs. To
identify which documents are about to expire in Microsoft 365, users can
run the former to receive email notifications about expiring documents.
To remove checkouts of documents that have already expired in Microsoft
365, users can run the latter to cancel documents that have been checked
out to Microsoft 365 for 180 days or more.
For product documentation, reference Microsoft 365 and Schedulable jobs.
Related work item(s): PLTFM-2715, PLTFM-2716, PLTFM-2787
Recalculate document sharing rules for groups
Document sharing rules determine which roles can access a document and are only applied when a new document is created. This means that if a group is added to an existing document, none of the sharing rules on the document will apply to the group members. To ensure that document sharing rules can be applied to group members who are added to a document after document creation, now provides the CM_CreateDocumentSharingRulesBatch class as a new batch job. This new batch job will allow users to recalculate document sharing rules for groups.
For product documentation, reference Document Roles and Document Sharing Rule Groups.
Related work item: PLTFM-2958
Mute document and workflow task notifications
Users can now mute the notifications that are sent out for documents and
workflow tasks. For document notifications, users assigned with document
roles that have the Mute Notifications (CM_Mute_Notifications)
Permission (mvn__CM_Permission__mdt) metadata record can mute system
event notifications for specific document types, states, and statuses.
To do so, users can configure the new Notifications Muted by Default
(mvn__CM_Notifications_Muted_by_Default__c) field on the Document
State (mvn__CM_Document_State__mdt) custom metadata type to manage the
default muting of notifications for a given document state or status. To
override the default setting, users must also have the Mute
Notifications permission to click Mute Notifications or Unmute
Notifications on the Document record.
Once configured, no document system event notifications will be sent out to any collaborators on the document, but workflow task notifications will continue to be sent. Further, if a document has its notifications muted, a notifications muted icon will appear after the title and state of the document; if a document has its notifications enabled, no icon will appear.
For workflow task notifications, users with access to the Notifications
Muted (mvn__CM_Notifications_Muted__c) field on the Activity object
can mute notifications for a Task record in the Start Workflow and Edit
Task modals. Task-level notification settings supersede document-level
notification settings such that users can send task notifications for a
document even if the document notifications are muted.
Note: Users with the CM_SystemAdmin or CM_ContentAuthor permission set assigned already have access to that field.
Related work items(s): MIC-3600, PLTFM-2294, PLTFM-2295, PLTFM-2717
New dedicated Veeva install page
There is now a dedicated Veeva install option in the . Veeva integrations are available separately and are not included by default. Upgrades will have the new open Veeva connectors installed but not activated.
Related work item: MIC-3561
Veeva Open Connectors
New Veeva connectors were written to be faster and more customizable. The new connectors can be updated by customers for exact control of their needs. They will be installed automatically in all orgs that had the previous Veeva connectors. For new installs, they are also available as a separate add-on install.
Related work item: MIC-3565
Updated features
The V15 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 E2B module
The E2B module was moved to a new, dedicated package (mic-e2b) and installer. The new package allows updates made to E2B processing to be released separately from the core package and lets customers choose if they want to install new E2B changes or retain their validated and known configurations. Because the module was moved to its own package, several changes were made throughout . These changes are noted below in their respective sections.
For information about the dedicated package and installer, reference E2B(R3) generation.
Related work item: MIC-3820
Optional document changelog
Currently, when users create a new document version or check in a
document, they are required to submit a changelog or enter a reason for
the change. To provide a more seamless experience of uploading and
checking in documents, admin users can now configure the "Please
provide a reason for change" field from required to optional via the
new Enable Changelog Requirement
(mvn__CM_Enable_Changelog_Requirement__c) field on the MCM Global
Setting (mvn__CM_Global_Setting__mdt) custom metadata type.
For product documentation, reference MCM Global Setting.
Related work item: PLTFM-2930
Fulfillments
Admins can now configure how many files are required for a fulfillment.
As such, a new Required Selections (MED_Required__c) field was added
to the Dynamic Fulfillment Setting
(MED_Dynamic_Fulfillment_Setting__mdt) custom metadata type. Admins
can configure this field to require all, exactly one document, at least
one document or leave it as optional.
Note: The All Required (Legacy) (
MED_All_Required) field only applies to the previous DocGen user interface. However, if the newMED_Requiredfield is not set, the value specified in theAll_Requiredfield will be used.
Related work item: MIC-2829
Updated locking framework
V15 now lets you configure the locking framework, allowing for more control and customizations. Locking is now part of the trigger action framework, meaning an individual object can have locking enabled or disabled using the Trigger Action.
Related work item: MIC-3760
Trigger action framework enhancements
Several enhancements were made to 's Trigger Action Framework (TAF).
-
All core triggers were converted to the new trigger framework interface. This allows for individual trigger control and the insertion of custom trigger executions between product triggers. Triggers for all SObjects (including MCM) were converted as well.
-
To ensure the reliability of TAF handling, a new Apex Class Namespace (
mvn__TAF_Apex_Class_Namespace__c) field was added to both the Trigger Action (mvn__TAF_Trigger_Action__mdt) and Trigger Finalizer (mvn__TAF_DML_Finalizer__mdt) custom metadata types.
For more information, reference Triggers.
Related work item(s): MIC-3793, MIC-3810, MIC-3708, MIC-3559, PLTFM-2814, PLTFM-2683
Improved document search
The document search experience was improved to return more results when
users perform a keyword search. First, searches against Document Version
(mvn__CM_Document_Version__c) records and Content Document
(ContentDocument) records are executed in separate queries so that the
maximum limit of records that can be returned applies to each object.
Second, the total search scope increased from the configurable limit, which defaults to 100 records, to 4,000 records. The 4,000-record limit includes the maximum limit of 2,000 records with an offset of another 2,000 records. The configurable display limit is enforced after the SOSL queries return all of the matching records.
The improved document search can also determine if there are matching records that cannot be returned due to SOSL limits or the configurable display limit. To do so, the system will perform an additional search without sharing and without any filters. If this returns 2,000 records, then the system assumes there may be more documents that could potentially match the user's search and will subsequently throw a "Search limit exceeded" warning.
Related work item: PLTFM-2866
Faster UUID generation
Salesforce's Summer '24 release introduced a new System.UUID class that generates faster universally unique identifiers (UUIDs) than 's At_UUID global class. The At_UUID class was therefore deprecated such that the getValue method still returns a valid UUID, but the formatValue, isValid, and valueOf methods will all throw exceptions. recommends migrating all uses of 's At_UUID class to Salesforce's System.UUID class. For more information, reference Salesforce's documentation on the UUID class.
Related work item: PLTFM-2895
Checking documents in
Users can now check a document in even if it is checked out by another
user, allowing them to continue working in the document. A new custom
permission, Check In Other Users Documents
(CM_Check_In_Other_User_Document), was created to facilitate this and
must be assigned to users wanting this capability.
Note: This also applies to documents that are checked out to Microsoft 365.
Related work item: PLTFM-2932
Show previous versions of related documents
A document can be related to multiple versions of another document, but only the latest version is shown in the Related Documents component by default. To show the older versions of the related documents, admin users can uncheck the new Hide Relationships to Previous Versions option in the Related Documents component.
For product documentation, reference Relationships.
Note: The Hide Relationships to Previous Versions option is "on" by default for all customers.
Related work item: PLTFM-2832
Edit metadata on checked out documents
Users with the Edit Metadata document permission can now modify the
metadata on documents that are checked out. Previously, checked out
documents were locked such that no user could edit the title,
description, or other details on the documents. In the new release,
admin users can check the new Enable Edit Metadata on Check Out
(mvn__CM_Enable_Edit_Metadata_Checkout__c) checkbox field on the
Default MCM Global Setting (mvn__CM_Global_Setting__mdt) metadata
record so that any user with the Edit Metadata document permission can
click Edit Details on checked out documents to edit the metadata.
Related work item: PLTFM-2473
Salesforce CTI support
CTI support was updated to allow the setting of arbitrary field values on Interactions when answering phone calls. It also now supports more flexible and robust default of Account Search criteria.
Related work item: MIC-3850
Additional enhancements
Additional enhancements can be found below.
Additional enhancements custom-style="sorted-asc-type-text-col-1"}
| Work item | Description | Version |
|---|---|---|
| MIC-2895 | Several UI components were updated in V15 from if:true and if:false to use the newer lwc:if syntax in an effort to move away from deprecated Salesforce APIs and use new replacements. | V15 |
| MIC-3560 | CMS sources now support searching and a CMS Custom Handler at the same time. | V15 |
| MIC-3811 | The list of available delivery methods on DocGen DDPs is now sorted using the Order field, rather than alphabetically. | V15 |
| MIC-3856 | The Add Interaction Related Items button is now available to add to the Product Quality Complaint and Fulfillment objects. Admins will need to manually add them to the layouts. | V15 |
| PLTFM-2587 | The Microsoft 365 experience has changed from being hosted on office.mcm.mavens.com to office.mcm.komodohealth.com and all environments have been migrated. | V15 |
| PLTFM-2725 | MCM workflows now support sending more notification emails (up to 200) at one time. | V15 |
Defect fixes and maintenance
The table below details defects and maintenance items identified in V14 and V14.1 that were fixed in the V15 release.
Fixed items
| Work item | Description | New behavior | Version fixed |
|---|---|---|---|
| MIC-3576 | The Request Document: FAQ Mapping flow was not handling rich text from correctly and was putting raw HTML into the question and answer fields. | This flow now uses text templates for rich text, resolving the issue. | V15 |
| MIC-3690 | Account Search results that were derived from external systems could not be opened. When users clicked a name in the results to open the account, an error page would appear stating the page does not exist. | The link attached to the name fields has been fixed and will work correctly as of the V15 release. | V15 |
| MIC-3728 | The E2B file generation was missing an author tag inside the H.2/3/4 components. | The missing author tag was added to the H.2/3/4 section of E2B. | V15 |
| MIC-3729 | The kindOfProduct tag was missing attributes in the E2B XML output. | The kindOfProduct tag has two attributes which now appear in the E2B output. | V15 |
| MIC-3740 | The Age Unit was previously hard-coded to years using the R2 value. This was incorrect and resulted in errors in the E2B XML output. | The Age Unit is no longer hard-coded and can be configured. | V15 |
| MIC-3742 | The ID tag was missing from the G.k.1 section. | The tag has been added to the E2B XML output. | V15 |
| MIC-3747 | The contents of the E2B D.7.1.r.5 field on the Adverse Event Medical History modal were not populating in the E2B XML. | Comments are now included in the E2B output when configured. | V15 |
| MIC-3757 | The E2B: Medical History Code tag for D.*7.1.r.1 was missing from E2B. | The tag has been added and allowing the E2B to generate successfully. | V15 |
| MIC-3758 | If the Country of Authorization (MED_Country_of_Authorization_Application__c) field on an Adverse Event drug was left blank or not mapped, the resulting XML would still have the G.k.3.2 code when it should not. | The XML now omits that code when the Country of Authorization field is blank or unmapped. | V15 |
| MIC-3759 | When a value of "Gender Unknown" was added to the Adverse Event Patient Gender (MED_Adverse_Event__c.MED_Patient_Gender__c) field, the code field was outputting UNK, which is invalid. | If D.5 specifies a nullFlavor as the value, the null flavor is now outputted using the correct syntax instead of being outputted as the value. | V15 |
| MIC-3771 | E2B: Boolean fields, like C.1.7, were being incorrectly handled and required R2 values for them to be outputted correctly. | The E2B: Boolean fields can now handle the proper R3 values and nulls correctly. | V15 |
| MIC-3783 | Text that was entered in the Patient Relevant Medical History (MED_Patient_Relevant_Medical_History__c) field was being duplicated for every medical history record when it should just appear once. | The text now only appears once. | V15 |
| MIC-3788 | Users encountered an error when attempting to reparent a Veeva address to a different account. This was because reparenting was not allowed on the Contact Information (MED_Contact_Information__c) and Affiliation (MED_Affiliation__c) objects. | Reparenting is now allowed on the Contact Information and Affiliation objects. | V15 |
| MIC-3800 | Users were getting a "Collection size exceeds maximum size of 1,000" error when trying to load more than 1,000 products on the Ad Hoc QA page. This was due to the Salesforce limit on Visualforce picklists. | The Ad Hoc QA page will now fall back to a standard lookup when there are too many products to put into a picklist. As such, the page will no longer throw an error when more than 1,000 general product records are loaded. | V15 |
| MIC-3806 | The Trigger Action Framework was not honoring non-namespaced permissions. | The Trigger Action Framework will honor non-namespaced custom permissions for trigger bypassing. | V15 |
| MIC-3830 | Sometimes when multiple search handlers are configured, an incorrect search object would be provided to the second search handler because the first handler modified it. | Query requests are no longer passed by reference so search handlers cannot accidentally modify it for other handlers. | V15 |
| MIC-3851 | The G.k.4.r.10.1 was a picklist when it should have been a free text field and only appeared in the output file if G.k.4.r.10.2a/b (TermId) were both populated. | This was fixed by adding a new Route of Administration (MED_Route_of_Administration_Text__c) field to the AE Drug (MED_AE_Drug_Information__c) custom object and will now be included in the output even if TermId is not used. | V15 |
| MIC-3900 | When users attempted to change the previously selected requestor, Account Search threw an error when the change was completed and the search window was closed. | This issue was fixed in V15 so that users do not see the error. | V15 |
| PLTFM-2150 | When performing a document search, if all of the documents matching the filter criteria do not have a document, an error occurs. This issue was detailed in KI-120. | Users can now see all results matching their filter criteria without encountering an error. | V15 |
| PLTFM-2689 | If a user has the necessary permissions to use the Microsoft 365 integration but the integration is not configured, the user can click the Microsoft 365 option in the Check Out Document modal but will be thrown a "Could not create file" error. | The Microsoft 365 option in the Check Out Document modal is now only enabled if all of the user, document, and configuration requirements are met for the Microsoft 365 integration. | V15 |
| PLTFM-2549 | The Manage Sharing (CM_Manage_Sharing) Permission (mvn__CM_Permission__mdt) metadata record determines which users can manage and modify document collaborator roles on a document. However, users who did not have the Manage Sharing document permission were able to delete document collaborator roles from a document. | Now, only users who have the Manage Sharing document permission are able to manage (e.g., delete) the roles of document collaborators on a document. | V15 |
| PLTFM-2721 | As part of Salesforce's Summer '24 release, Salesforce updated the content security policy (CSP) directives for Lightning pages. This prevents Microsoft 365 domains that are embedded as iframes in Lightning pages from loading and may prompt errors in users' browsers. This issue was previously identified in KI-127. | Microsoft 365 domains are now packaged as trusted sites such that all of the trusted URLs listed in the workaround of the known issue (KI) are provided out of the box. | V15 |
| PLTFM-2896 | If a user views a Document Version (mvn__CM_Document_Version__c) record, the standard Last Modified By (LastModifiedById) field updates with the user's information, even if the user didn't actually edit the document version. This is because the URL to view the most recently rendered preview is stamped on the Thumbnail URL (mvn__CM_Thumbnail_URL__c) field on the Document Version record to render the thumbnail in list views. The stamping of the URL is what updates the Document Version record and therefore what causes the user who viewed the document version to be set on the Last Modified By field. This issue was previously identified in KI-127. | When a user views a Document Version record, the URL that renders the latest document preview is no longer stamped on the Thumbnail URL field. Instead, the URL is generated automatically on the Thumbnail (mvn__CM_Thumbnail__c) formula field. This means that the Thumbnail URL field is superseded by the Thumbnail field and will be deprecated. This also means that the user who viewed the document can no longer be set on the Last Modified By field if they did not actually edit the document version. | V15 |
| PLTFM-2924 | When a user performs a document search and then sorts the records returned, the user may see documents in the sorted view that were not in the initial search results. This is because all of the documents retrieved from the search query are sorted, not just the limited number of documents that were returned as results. | Sorting the returned records of a document search now only affects the documents that appear in the initial search results, not all of the documents retrieved from the search query. This means that users will always see the same set of documents no matter if or how they sort the results, just in a different order. | V15 |
| PLTFM-2997 | Upon upgrading to Salesforce's Winter '25 release, the close button for modals now appear as a white square instead of a white X. For more information, reference Salesforce's Lightning Design System release notes. This issue was also detailed in KI-128. | The close button now appears as a white X, rather than a white square. | V15 |
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.
Apex classes
Apex class changes are listed in the table below:
New Apex classes
| Work item(s) | API name |
|---|---|
| PLTFM-2715, PLTFM-2716, PLTFM-2787 | CM_CancelExpiredCheckedOutDocumentsBatch CM_CheckOutExpirationSchedulable |
| PLTFM-2958 | CM_CreateDocumentSharingRulesBatch |
Custom labels
Custom label changes are listed in the tables below:
New custom labels
| Work item | Custom label |
|---|---|
| MIC-3600 | CM_Document_Muted |
| CM_Document_Muted_By_State | |
| CM_Mute_Notifications_For_Workflow | |
| PLTFM-2294 | CM_Mute_Document_Level_Notifications |
| CM_Mute_Notifications_Success | |
| CM_permission_mute_notifications | |
| CM_Unmute_Document_Level_Notifications | |
| CM_Unmute_Notifications_Success | |
| PLTFM-2295 | CM_Mute_Notifications |
| PLTFM-2715 | CM_Check_Out_Expiry_Body_Template |
| CM_Check_Out_Expiry_Subject_Template | |
| CM_Check_Out_Expiry_Title_Template | |
| PLTFM-2717 | CM_Document_Muted |
| CM_Document_Muted_By_State | |
| CM_Mute_Notifications_For_Workflow | |
| PLTFM-2832 | CM_Hide_Previous_Versions |
Custom metadata types
Custom metadata type changes are listed in the tables below:
New custom metadata type fields
| Work item | Custom metadata type | Field | Description |
|---|---|---|---|
| MIC-2829 | MED_Dynamic_Fulfillment_Setting__mdt | MED_Required__c | Required document selection for job based fulfillment generation. If not set, falls back to the value specified in MED_All_required. |
| MIC-3600, PLTFM-2717 | mvn__CM_Document_State__mdt | mvn__CM_Notifications_Muted_by_Default__c | Used for muting document notifications based on document status/state. Used as a default value but can be overwritten via UI. |
| MIC-3760 | mvn__MED_Global_Setting__mdt | mvn__MED_Locking_Rules_Class__c | Used to specify the Apex class for locking rules. |
| MIC-3820 | MED_E2B_Setting__mdt | MED_Include_Files__c | Determines whether or not the E2B files includes attachments from the Adverse Event. This is on by default. |
| PLTFM-2473 | mvn__CM_Global_Setting__mdt | mvn__CM_Enable_Edit_Metadata_Checkout__c | Allows users with the Edit Metadata document permission to modify document metadata while the document is checked out. |
| PLTFM-2814 | mvn__TAF_Trigger_Action__mdt | mvn__TAF_Apex_Class_Namespace__c | Enter the Apex class namespace. |
| PLTFM-2814 | mvn__TAF_DML_Finalizer__mdt | mvn__TAF_Apex_Class_Namespace__c | Enter the Apex class namespace. |
| PLTFM-2930 | mvn__CM_Global_Setting__mdt | mvn__CM_Enable_Changelog_Requirement__c | Flag controlling whether or not a user is required to fill out a change log when creating a new document version or checking in a document. Defaulted to true. |
New custom metadata records
| Work item | Custom metadata type | Metadata record name |
|---|---|---|
| PLTFM-2294 | mvn__CM_Permission__mdt | CM_Mute_Notifications |
Objects
Object changes are listed below.
New objects
| Object name | API name | Description |
|---|---|---|
| Workflow Instance Activity Content | mvn__CM_Workflow_Instance_Activity_Content__c | Junction object to assist in including workflow instance content attachments as attachments to system event notifications. |
New object fields
| Work item | Object | Field |
|---|---|---|
| MIC-3793 | EmailMessage | mvn__MED_Locked__c mvn__MED_Override_Lock__c |
| MIC-3851 | AE Drug | MED_Route_of_Administration_Text__c |
| PLTFM-2294 | mvn__CM_Document__c | mvn__CM_Mute_Document_Level_Notifications__c |
| PLTFM-2295 | Activity | mvn__CM_Notifications_Muted__c |
Modified object fields
| Work item | Object | Field | Modification description | Version modified |
|---|---|---|---|---|
| PLTFM-2896 | mvn__CM_Document_Version__c | mvn__CM_Thumbnail__c | The field will be repurposed to generate the URL of the most recently rendered preview of the document version. This field will supersede the Thumbnail URL (mvn__CM_Thumbnail_URL__c) field, which will be deprecated. | V15 |
Permissions
Permission changes are listed in the table(s) below:
New permission sets
| Work item | Permission set | Version added |
|---|---|---|
| MIC-4887 | MED_E2B_User | V15 |
New custom permissions
| Work item | Custom permission | Version added |
|---|---|---|
| PLTFM-2932 | CM_Check_In_Other_User_Document | V15 |
Modified permission sets
| Work item | Permission set | Modification description |
|---|---|---|
| PLTFM-2295 | CM_ContentAuthor CM_SystemAdmin | The permission sets will be modified to include read and edit access to the new Notifications Muted (mvn__CM_Notifications_Muted__c) field on the Task object. |
Trusted URLs
Trusted URL changes are listed in the table below:
New trusted URLs
| Work item | API name | URL |
|---|---|---|
| PLTFM-2721 | CA_Microsoft_365 | *.mcm.komodohealth.com |
| CA_Microsoft_365_Auth | mcm.auth.us-west-1.amazoncognito.com | |
| CA_Microsoft_365_Auth_Mavens | *.mcm.auth.mavens.com | |
| CA_Microsoft_365_Auth_TEST | mcm--staging.auth.us-west-1.amazoncognito.com | |
| CA_Microsoft_365_Mavens | *.mcm.mavens.com |
Deprecated and deleted items
The following entities have either been deprecated or deleted from the latest release of and will no longer be available or supported in future releases.
Deprecated custom metadata type fields
| Work item | Custom metadata type | Field |
|---|---|---|
| MIC-3820 | MED_Global_Setting__mdt | MED_Use_Files__c |
Deprecated object fields
| Work item | Object | Field | Description |
|---|---|---|---|
| PLTFM-2896 | mvn__CM_Document_Version__c | mvn__CM_Thumbnail_URL__c | Relative URL of the thumbnail rendition. |
Post-upgrade required actions
This section includes the required actions administrators must take after upgrading to V15. Each required action specifies the criteria for consideration, which details the conditions that must exist to warrant action by a customer.
E2B
If using E2B:
-
Assign all users the new MED_E2B_User permission set, by permission set group (recommended).
-
Check that the
E2B_Settings__mdt.Include_Files__cmatches the deprecatedMED_Global_Setting__mdt.MED_Use_Files__ccheckbox.
Additional requirements: If you are using E2B and
MED_Global_Setting__mdt.MED_Use_Files__c is unchecked:
- You will need to update your integration to pull E2B Files from the related Salesforce Files (ContentDocument) instead of Attachments.
Migrate to Veeva Open Connectors
If using the previous Veeva Connectors, it is recommended to migrate to the new Veeva Open Connectors as the legacy connector support will be ending. Migration scripts to move between the Legacy and Veeva Open Connectors are available at the , install.komodohealth.com.
Delivery methods on DocGen Dynamic Document Packages (DDPs)
Admins should make sure that the delivery options order is the correct order they want to display.