Fall '24 release notes
This topic contains the release notes for the Fall '24 release of Komodo Publications Planning. The release notes are organized into these high-level sections:
Installation – link to install and/or upgrade to the new version.
New features – new features and functionalities in the new version.
Updated features – updated features and functionalities in the new version.
Collaborator Portal updates – updated features and functionalities in the Collaborator Portal.
Defect fixes and maintenance – defects and maintenance items fixed in the new version.
Metadata changes – changes to the underlying data models, user permissions, or system configurations in the new version.
Deprecated and deleted items – components of the product that have been deprecated, removed, or retired in the new version.
Required post-upgrade actions – required actions administrators must take after upgrading to the new version.
To identify if a feature request you made is included in this release, search these release notes 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, Komodo Health 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.
For the release notes from earlier versions of Komodo Publications Planning, visit the Archive.
Installation
The Komodo Publications Planning Fall '24 release can be installed with the Komodo Install Service at https://install.komodohealth.com/products/kpp/latest. New installs of Komodo Publications Planning will be on the latest release while current customers will need to run and deploy the latest update.
Warning
Current customers who upgrade to the latest Fall '24 release must remember to complete the steps in the Required post-upgrade actions section below.
New features
The new release of Komodo Publications Planning contains several new features whose functionalities are detailed below. Details about enablement and configuration are included within the product documentation.
Manage expiring and expired documents checked out to Microsoft 365
Documents that are 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, Komodo Publications Planning 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 Check out a document and Schedulable jobs.
Related work item(s): PLTFM-2715, PLTFM-2716, PLTFM-2787
Installable reports, report types, and dashboards
The Komodo Install Service now has an optional step for you to install several out-of-the-box (OOTB) reports, report types, and dashboards into your Salesforce environment. Users can clone and edit these resources to fit their specific business needs.
Related work item(s): MPP-2635
(Beta) Enhanced timeline visualization
The Komodo Install Service offers a new Visualizations package that can be installed into your Salesforce environment to provide a configurable Gantt chart visualization as a Timeline (khvTimelineWrapper) component. This component can be used on any sObject's record page, can be configured for any Salesforce data structure, and is customizable and interactive. It can therefore be used in place of Komodo Publications Planning's current Timeline (ppTimelineWrapper) component.
Warning
The Visualizations package is a Beta product for early adopters who are interested in trying out the enhanced timeline visualization and will only be available for manual installation via the Komodo Install Service with Komodo Publications Planning's Fall '24 release.
Updated features
The new release of Komodo Publications Planning 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.
Greater visibility on primary targets
Target (mvn__PP_Target__c) records whose Primary (mvn__PP_Primary__c) field is checked (true) has been made more prominent throughout the Komodo Publications Planning product. For instance, Target records in the Targets related list (ppDocumentTargetsRelatedList) are now sorted first by the Primary checkbox field and then by the Priority (mvn__PP_Priority__c) picklist field. This means that any target that is marked as primary appears at the top of the related list while any target that is otherwise marked as preferred, alternate, or considered appears later in the related list in that particular order. Additionally, the Primary field replaces the Priority field in the Targets related list, the Targets list view, the default Target search layout, and the Komodo Publications Planning Document page layout. These updates enable users to have greater visibility on their primary target congresses and journals over other preferred, alternate, and considered targets. For product documentation, reference Sort order.
Related work item(s): MPP-2340, MPP-2417
Migration of the Microsoft 365 experience
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 accordingly. This does not disrupt existing customers from using Microsoft 365 in Komodo Publications Planning. Additionally, most references to "Office 365" throughout the Komodo Publications Planning product and documentation have been replaced with "Microsoft 365".
Related work item(s): PLTFM-2587, PLTFM-2723
Updated muting functionality for document notifications
Several enhancements have been made available for the muting functionality of document and workflow task notifications.
Mute notifications for document collaborators
Users with the Mute Notifications (CM_Mute_Notifications) Permission (mvn__CM_Permission__mdt) metadata record are now able to mute notifications for individual document collaborators on a given document. A new Notifications? (mvn__PP_Notifications__c) field has been added to the Document Collaborator (mvn__PP_Document_Author__c) object and a new corresponding Notifications column is available in the Document Collaborators related list. By default, every document collaborator that is added to a document has notifications enabled and a blue notifications (
) icon in the Notifications column. However, users with the Mute Notifications permission can click the icon to mute notifications for the document collaborator. The blue notifications icon will change to a grey notifications muted (
) icon, and the document collaborator will no longer receive notifications for the document or any of the document's workflow tasks. Users with the Mute Notifications permission can revert the muting of notifications for the document collaborator by clicking the icon again. If the document has notifications muted, the document collaborator will not receive any notifications even if they have notifications enabled. For product documentation, reference Mute notifications.
Related work item(s): MPP-2492
Mute notifications for document states and statuses
Users with the Mute Notifications (CM_Mute_Notifications) Permission (mvn__CM_Permission__mdt) metadata record are now also be able to mute notifications for a document based on the document's state or status. 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. For product documentation, reference Disable notifications.
Related work item(s): PLTFM-2717
Improved UI/UX for muting notifications
The UI/UX of the muting functionality for document and workflow task notifications has also been enhanced. 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. Additionally, the checkbox to mute notifications for a workflow task has been relabeled from "Mute Notifications" to "Mute notifications for this workflow" and is configurable via the CM_Mute_Notifications_For_Workflow custom label.
Related work item(s): PLTFM-2717
Improved performance for task attachments
The adding of content attachments from workflow instances to system event notifications is now handled by the new Workflow Instance Activity Content (mvn__CM_Workflow_Instance_Activity_Content__c) object instead of the standard Content Document Link (ContentDocumentLink) object. The new object increases the performance of attaching files to email notifications for workflow tasks. For product documentation, reference Workflow Instance Activity Content.
Related work item(s): PLTFM-2724
Improved document search
The document search experience has been 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 now execute in separate queries so that the maximum limit of records that can be returned applies to each individual object. Second, the total search scope has increased from the configurable limit, which defaulted 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 will be enforced after the SOSL queries return all of the matching records.
The improved document search also determines if there are matching records that cannot be returned due to SOSL limits or the configurable display limit. To do so, the system performs an additional search without sharing and without any filters. If this returns 2,000 records, then the system assumes that there are more documents that could potentially match the user's search and will subsequently throw a "Search limit exceeded" warning to the user.
Related work item(s): PLTFM-2866, PLTFM-2925
Faster UUID generation
Salesforce's Summer '24 release introduced a new System.UUID class that generates faster universally unique identifiers (UUIDs) than Komodo Publications Planning's At_UUID global class. The At_UUID class has therefore been deprecated such that the getValue method still returnd a valid UUID, but the formatValue, isValid, and valueOf methods all throw exceptions. Komodo Health recommends migrating all uses of Komodo Publications Planning's At_UUID class to Salesforce's System.UUID class. For more information, reference Salesforce's documentation on the UUID class.
Related work item(s): PLTFM-2895
Optional document changelog
When users create a new document version or check in a document, they were previously required to submit a changelog or enter a reason for the change. To create a more seamless experience of uploading and checking in documents, admin users can now configure the "Please provide a reason for change" field to be either required or optional. To do so, admin users can use 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(s): PLTFM-2930
Check in documents for other users
Users are now able to check in documents that are checked out by other document collaborators, including documents that are checked out to Microsoft 365, to continue their work. Users who wish to have this capability must be assigned the new custom permission, Check In Other Users Documents (CM_Check_In_Other_User_Document).
Related work item(s): PLTFM-2932
Recalculate document sharing rules for groups
Document sharing rules determine which roles have access to 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 members of the group. To ensure that document sharing rules can be applied to group members who are added to a document after document creation, Komodo Publications Planning now provides the CM_CreateDocumentSharingRulesBatch class as a new batch job. This new batch job allows users to recalculate document sharing rules for groups. For product documentation, reference Recalculate sharing and Document Sharing Rule Groups.
Related work item(s): PLTFM-2958
Improved functionality for completing workflow tasks
Several updates have been made to enhance the existing functionality of completing workflow tasks.
Reassign a task to another user
Previously, a document collaborator could not reassign their workflow task unless they had the CM_Admin custom permission or asked a user who had the CM_Admin custom permission. Now, document collaborators can reassign their workflow tasks to other users without needing administrator access. Instead, document collaborators need the new CM_Reassign_Task custom permission, which is included in the CM_ReassignTasks permission set. For product documentation, reference Complete a task.
Related work item(s): PLTFM-2931
Complete a task for another user on the Task record
If a document collaborator wanted to complete a workflow task on behalf of the task assignee, the document collaborator had to mark the task as complete on the Document record because they could not do so on the Task record. In this new release, the ✓ Complete Task button appears on the Task record if the feature is enabled and the document collaborator has the required permissions. This means that users can now complete tasks on the Task detail page in addition to the Document record page. For product documentation, reference Complete a task.
Related work item(s): PLTFM-2961
Maintain task ownership when task is completed by another user
Previously, when a document collaborator completed a workflow task on behalf of the intended assignee, the document collaborator became the owner of the task and the original assignee would lose access to the task. This was a known issue (KI) that was documented in KI-129 and has now been fixed. The feature has also been improved. Going forward, the Owner Name (mvn__CM_Owner_Name__c) field on the Task record will no longer be updated to show the user who completed the task and will only contain the user who is assigned the task and therefore owns the task. Instead, the new Completed By (mvn__CM_Completed_By__c) field and the new Completed By Name (mvn__CM_Completed_By_Name__c) field will be added to the Activity standard object to denote the user who completed the task. If the document collaborator who completes the task is not the user who was assigned and owns the task, then the Completed By field will show "<name of document collaborator> on behalf of <name of task assignee>". This ensures that the original task assignee maintains ownership and access to the task, that the document collaborator who completed the task is properly tracked, and that there is a clear indication on whether or not the user collaborator who completed the task is the same as the user who was assigned the task. For product documentation, reference Complete a task.
Related work item(s): PLTFM-2975
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 scroll to the values that started with f and then scroll to the values that started with r. In this 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.
Related work item(s): PLTFM-2979
Collaborator Portal updates
The new release of Komodo Publications Planning also includes a new version of the Collaborator Portal. The updated Collaborator Portal contains several enhancements to existing functionalities as well as improvements to the user interface and user experience (UI/UX). Unless noted otherwise, all updated features are shipped "off" by default for existing customers and "on" by default for new customers.
Passwordless login
Admin users are now able to enable passwordless login for the Collaborator Portal via the new Enable Passwordless Login (mvn__PP_Enable_Passwordless_Login__c) field on the Collaborator Portal (mvn__PP_Collaborator_Portal__mdt) custom metadata type. With passwordless login, document collaborators will no longer be required to set and enter a password to log into and use the Collaborator Portal. Instead, document collaborators will only need to enter an email address to receive a verification code to authenticate into the Collaborator Portal. For product documentation, reference Enable passwordless login.
Related work item(s): MPP-2430, MPP-2457, MPP-2516, MPP-2544, MPP-2607, MPP-2608
Tabular view for publications
Collaborator Portal users are now able to switch between the existing card view and a new tabular view in the My Publications tab. The card view is the default view for both active and archived publications, but users can click on a grid (
) icon and a table (
) icon to switch between the card view and the tabular view, respectively. In the tabular view, users can sort the list of publications by each of the available columns, including, but not limited to, the name, status, and target date of the publication. Additionally, "archived" publications has been renamed as "inactive" publications. For product documentation, reference Publication documents.
Related work item(s): MPP-2525, MPP-2605
Consolidation of related documents
The Package Files tab and the Supporting Documents tab have been combined into a new Related Documents tab so that all documents related to a publication document are consolidated into a single view. Package files and supporting documents are still separated into two separate sections within the Related Documents tab to distinguish between the different types of related documents. Additionally, the buttons to download and open package files now resemble those for supporting documents to maintain a more uniform design across the Collaborator Portal. A 
File button will download the selected related document while an 
Open File button will open the related document in Microsoft 365. For product documentation, reference Collaborator Portal documents.
Related work item(s): MPP-2528
Updated buttons for downloading and opening publication documents
The buttons in the Collaborator Portal for downloading and opening publication document files have been updated to have more intuitive and user-friendly icons and labels. Previously, the icons for both the Open in Office 365 button and the Open Package Files in Office 365 button for publication documents were the same and the label on the Download All button did not specify which files would be downloaded. In this new release, there is a Pub button to download the publication document, a 
Pub & Package Files button to download the publication document along with any package files, and an Open Pub button to open the publication document in Microsoft 365. The unique icons and clear labels make it easier for users to understand what all of the buttons do.
These three buttons are also available for each review and approval task in both the task row as well as the task completion modal. This allows external document collaborators to more easily access the documents that they may need to complete their assigned reviews and approvals. If there are no package files associated with the publication document or if Microsoft 365 is not available in the Collaborator Portal, then the corresponding button will be disabled (i.e., greyed out) so that users cannot click on them. If there is no file for the publication document, then all of the buttons will be disabled.
Additionally, publication documents that are checked out to Microsoft 365 can still be downloaded in the Collaborator Portal without configuration. As a result, the Enable Checked Out Document Download (mvn__PP_Enable_Checked_Out_Document_Download__c) field on the Collaborator Portal (mvn__PP_Collaborator_Portal__mdt) custom metadata type has been deprecated.
For product documentation, reference Publication documents.
Related work item(s): MPP-2526, MPP-2529, MPP-2629
Updated Digital Science OAuth scope
In response to Digital Science's updated authentication flow as well as Salesforce's improved named credentials, Komodo Publications Planning has updated the Open Authorization (OAuth) scope and configuration steps for integrations with Digital Science. The legacy named credential for Digital Science no longer functions. For product documentation, reference Digital Science.
Warning
If you are a current customer who uses Digital Science, you must complete the updated configuration steps to maintain your Digital Science integration. For more information, reference the Required post-upgrade actions below.
Related work item(s): MPP-2680
Defect fixes and maintenance
Table 4, “Fixed items” details defects and maintenance items identified in Komodo Publications Planning Spring '24 that are fixed in Komodo Publications Planning Fall '24.
Work item | Description | New behavior |
|---|---|---|
MPP-2202 | If a user was using a 13-inch screen and created a new document collaborator where the selected Record Type ID equaled | The Document Collaborator Search wizard is now scrollable so that the wizard's height adjusts to the user's screen size and users can access all of the fields on the form. |
MPP-2203 | When a user created a new document collaborator, the Country field in the Document Collaborator Search wizard ( | The Country field in the Document Collaborator Search wizard is required for all new document collaborators that a user creates, regardless of the selected record type. |
MPP-2204 | In the Document Collaborator Search modal, the refresh ( | When users click the refresh ( |
MPP-2309 | When an external document collaborator was assigned a workflow task to review or approve a document, the external document collaborator was only given read access to the document and therefore could not complete the task. | Two Document State Role Permission ( |
MPP-2313 | When a user performed advanced search to find a target congress and only entered either a start date or an end date, an "Invalid bind expression type of String for column of type Date" error message appeared. | Users are able to enter a congress date filter with a single date; the error message no longer appears. |
MPP-2411 | When a user clicked the Targets header link on the Targets related list, the user was brought back to the top of the current page. | Users who click the Targets header link on the Targets related list will be taken to a new tab that contains the Targets list view. |
MPP-2567 | If a plan team member of a publication plan created a document, related the document to the publication plan, and provisioned all plan team members access to the document, the plan team member who created the document appeared as two separate document collaborators. One document collaborator had the Owner role while the other document collaborator had the role the plan team member assigned to themselves, which could be another Owner role. NoteThis issue was first identified in KI-122 and partially addressed in the Komodo Publications Planning Spring '24 1.32.0.1 hotfix. | Every plan team member who is provisioned access to a document through a publication plan will only appear as one document collaborator on the document. |
MPP-2681 | When there were 20 or more document collaborators on a document and a user hovered over a user type icon in the Document Collaborators related list, the tooltip for the icon appeared rows below the row that was hovered over. | The user type tooltip always appears near the user's cursor. |
MPP-2685 | When a user was assigned a task that was not related to a document and task notifications were enabled, the task called the system event service, the service errored out, and a debug log was created. | Tasks that are not related to a document should not, and will no longer, call the system event service. |
MPP-2691 | When a Collaborator Portal user sorted their open tasks by the Document # column, the user encountered an "Error when rendering Tasks" message. | The Collaborator Portal has been updated to allow users to sort tasks based on a field on a related record. This includes the Document # column, which sorts tasks using the Document Number ( |
MPP-2706 | When a user’s Open Authorization (OAuth) token for the Collaborator Portal became stagnant, such as when it expired before the user started their session, the OAuth token did not get refreshed properly. This allowed the user to log into the Collaborator Portal but also prompted an "invalid_client" or "invalid session" error message to appear. NoteThis issue was previously identified in KI-130. | Salesforce will automatically log out users who no longer have active OAuth sessions, so the error messages will no longer appear after users log into the Collaborator Portal. |
PLTFM-2289 | When an auto-start workflow was canceled and then manually restarted with more than one task assignee, the workflow was only assigned to the first task assignee. | Auto-start workflows that are canceled and then manually restarted will be assigned to all task assignees accordingly. |
PLTFM-2418 | When a new document was created with an external link or when an existing document with an external link was cloned, the Open URL button in the third and final step (i.e., the | For any document created by or cloned with an external link, users will be able to click the Open URL button in the final step of the Document Wizard to open and review the linked document in a new browser page. |
PLTFM-2580 | Data tables (i.e., the ppDatatable Lightning component) did not display any translated labels of picklist values. | Data tables display all configured translations of picklist values. |
PLTFM-2581 | When users deleted a role from a document collaborator on a document, the Assigned Roles ( | When users add or remove roles for document collaborators on a document, the Assigned Roles field updates accordingly. This ensures that each document collaborator is associated with the correct Role ( |
PLTFM-2689 | If a user had the necessary permissions to use the Microsoft 365 integration but the integration was not configured, the user could click the Microsoft 365 option in the Check Out Document modal but would be thrown a "Could not create file" error. | The Microsoft 365 option in the Check Out Document modal will only be enabled if all of the user, document, and configuration requirements are met for the Microsoft 365 integration. |
PLTFM-2721 | As part of Salesforce’s Summer ’24 release, Salesforce updated the content security policy (CSP) directives for Lightning pages. This prevented Microsoft 365 domains that were embedded as iframes in Lightning pages from loading and prompted errors in users' browsers. NoteThis issue was previously identified in KI-121. | 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 in Komodo Publications Planning out of the box. |
PLTFM-2851 | When a user muted notifications for a document, the user still received notifications for auto-start workflow tasks that they were assigned to on the document. | If a user has document notifications muted, the user will not receive any notifications for workflow tasks that they are assigned to on the document and that are configured to start automatically. |
PLTFM-2896 | When a user viewed a Document Version ( NoteThis 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 will be generated automatically on the Thumbnail ( |
PLTFM-2899 | When a user sorted a list of documents by the Document column, the order of the records did not accurately reflect the document numbers. | Sorting a list of documents by the Document column will order the records based on their document numbers. |
PLTFM-2924 | When a user performed a document search and then sorted the records returned, the user may have seen documents in the sorted view that were not in the initial search results. This was because all of the documents retrieved from the search query were sorted, not just the limited number of documents that were returned as results. | Sorting the returned records of a document search will only affect 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. |
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 would be 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 would lose 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 will keep their role on the document while the new assignee will also be granted the role to complete the task. |
PLTFM-2997 | Upon upgrading to Salesforce’s Winter ’25 release, the close button for modals appeared as a white square instead of a white X. NoteThis issue was previously identified in KI-128. | The close button now appears as a white X rather than a white square. |
Metadata changes
The following subsections capture the changes against entities in key areas of Komodo Publications Planning that are introduced in the latest release. This list is not exhaustive, as it does not contain changes that are internal to the application and that will not be exposed to customers for customization, extension, or integration.
Apex class changes are listed in the table(s) below:
Work item(s) | Apex class |
|---|---|
PLTFM-2715, PLTFM-2716, PLTFM-2787 | CM_CancelExpiredCheckedOutDocumentsBatch CM_CheckOutExpirationSchedulable |
PLTFM-2958 | CM_CreateDocumentSharingRulesBatch |
Work item(s) | Apex class | Description |
|---|---|---|
PLTFM-2895 | At_UUID | Generates universally unique identifiers (UUIDs). |
Custom label changes are listed in the table(s) below:
Work item | Custom label |
|---|---|
MPP-2430, MPP-2457, MPP-2516, MPP-2544, MPP-2607, MPP-2608 | PP_Blank_Verification_Code PP_Continue PP_Email_Address_Required PP_Invalid_Verification_Code PP_Invalid_Verification_Title PP_Login_With_Password PP_Login_Without_Password PP_Resend_Verification_Code PP_Resend_Verification_Code_Error PP_Resent_Verification_Code PP_Resent_Verification_Code_Title PP_Send_Verification_Code PP_Skip_This_Step PP_Success PP_Successful_Verification_Title PP_Verification_Code PP_Verification_Email_Sent PP_Verification_Title |
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 |
Work item | Custom label | Modification description |
|---|---|---|
PLTFM-2723 | CM_Cancel_O365_Check_Out_Confirmation_Message CM_Check_In_From_Office_365 CM_Check_In_From_Office_365_Confirm CM_Check_Out_Office_365_Description CM_Check_Out_Office_365_Label CM_Check_Out_Office_365_Success CM_Force_Check_In_Modal_Message CM_Office_365 CM_Office_365_Disclaimer CM_Office_Check_In_Lock_Error CM_Office_Check_Out_File_Extension_Error CM_Open_In_Office_365 | All instances of "Office 365" will be replaced with "Microsoft 365" in the default values of the custom labels. |
Custom metadata type changes are listed in the table(s) below:
Work item | Custom metadata type | Field |
|---|---|---|
MPP-2430 | mvn__PP_Collaborator_Portal__mdt | mvn__PP_Enable_Passwordless_Login__c |
MPP-2608 | mvn__PP_Collaborator_Portal__mdt | mvn__PP_Collaborator_Portal_Name__c |
PLTFM-2717 | mvn__CM_Document_State__mdt | mvn__CM_Notifications_Muted_by_Default__c |
PLTFM-2930 | mvn__CM_Global_Setting__mdt | mvn__CM_Enable_Changelog_Requirement__c |
Work item | Custom metadata type | Metadata record name |
|---|---|---|
MPP-2309 | mvn__CM_Document_State_Role_Permission__mdt | PP_Pub_In_Aprvl_Author_Edit_Doc PP_Pub_In_Review_Author_Edit_Doc |
Work item | Custom metadata type | Modification description |
|---|---|---|
PLTFM-2723 | mvn__CA_Office_365_Setting__mdt | The custom metadata type will be renamed from "Office 365 Setting" to "Microsoft 365 Setting". |
Work item | Custom metadata type | Field | Modification description |
|---|---|---|---|
MPP-2608 | mvn__PP_Pubs_Notification_Resource__c | mvn__PP_Pubs_Identity_Resource__c | The field label will be renamed from "Static Resource Name" to "Identity Static Resource Name". |
mvn__PP_Pubs_Notification_Resource__c | The field label will be renamed from "Static Resource Name" to "Notifications Static Resource Name". |
Work item | Custom metadata type | Field | Description |
|---|---|---|---|
MPP-2526 | mvn__PP_Collaborator_Portal__mdt | mvn__PP_Enable_Checked_Out_Document_Download__c | When |
MPP-2680 | mvn__PP_Digital_Science_Setting__mdt | mvn__PP_URL__c | The URL that is used when accessing Digital Science's API. |
Lightning component changes are listed in the table(s) below:
Work item | Lightning component | Modification description |
|---|---|---|
MPP-2340 | ppDocumentTargetsRelatedList | A sort order will be added to the related list. |
Object changes are listed in the table(s) below:
Work item | Object |
|---|---|
PLTFM-2724 | mvn__CM_Workflow_Instance_Activity_Content__c |
Work item | Object | Field |
|---|---|---|
MPP-2492 | mvn__PP_Document_Author__c | mvn__PP_Notifications__c |
PLTFM-2975 | Activity | mvn__CM_Completed_By__c mvn__CM_Completed_By_Name__c |
Work item | Object | Field | Modification description |
|---|---|---|---|
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 ( |
PLTFM-2975 | Activity | mvn__CM_Owner_Name__c | The field will be updated to only show the name of the user who is assigned and owns the workflow task. |
Work item | Object | Field set(s) | Modification description |
|---|---|---|---|
MPP-2417 | mvn__PP_Target__c | mvn__PP_Target_Related_List_Congress mvn__PP_Target_Related_List_Journal | The Primary ( |
MPP-2492 | mvn__PP_Document_Author__c | mvn__PP_Related_Document_Authors_Fields | The new Notifications? ( |
PLTFM-2975 | Task | mvn__CM_Task_Detail_Layout | The Original Assignee ( |
mvn__CM_Task_Tile_Layout | The new Completed By ( |
Work item | Object | Page layout | Modification description |
|---|---|---|---|
MPP-2417 | mvn__CM_Document__c | PP_Document_Layout | The Primary ( |
Work item | Object | Search layout | Modification description |
|---|---|---|---|
MPP-2417 | mvn__PP_Target__c | Default Layout | The Primary ( |
Work item | Object | Field | Description |
|---|---|---|---|
PLTFM-2896 | mvn__CM_Document_Version__c | mvn__CM_Thumbnail_URL__c | Relative URL of the thumbnail rendition. |
Permission changes are listed in the table(s) below:
Work item | Permission set |
|---|---|
PLTFM-2931 | CM_ReassignTasks |
Work item | Custom permission |
|---|---|
PLTFM-2931 | CM_Reassign_Task |
PLTFM-2932 | CM_Check_In_Other_User_Document |
Work item | Permission set | Modification description |
|---|---|---|
MPP-2606 | PP_ContentAuthor_External | The permission set will include the Document ( |
Work item | Custom permission | Modification description |
|---|---|---|
PLTFM-2723 | CA_Office_365_Admin | The custom permission will be renamed from "Office 365 Admin" to "Microsoft 365 Admin". |
CA_Office_365_User | The custom permission will be renamed from "Office 365 User" to "Microsoft 365 User". |
Trusted URL changes are listed in the table(s) below:
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 Komodo Publications Planning and are no longer available or supported in future releases.
Work item(s) | Apex class | Description |
|---|---|---|
PLTFM-2895 | At_UUID | Generates universally unique identifiers (UUIDs). |
Work item | Custom metadata type | Field | Description |
|---|---|---|---|
MPP-2526 | mvn__PP_Collaborator_Portal__mdt | mvn__PP_Enable_Checked_Out_Document_Download__c | When |
MPP-2680 | mvn__PP_Digital_Science_Setting__mdt | mvn__PP_URL__c | The URL that is used when accessing Digital Science's API. |
Work item | Object | Field | Description |
|---|---|---|---|
PLTFM-2896 | mvn__CM_Document_Version__c | mvn__CM_Thumbnail_URL__c | Relative URL of the thumbnail rendition. |
Required post-upgrade actions
This section includes the required actions administrators must take after upgrading to the Komodo Publications Planning Fall '24 release. Each required action specifies the criteria for consideration, which details the conditions that must exist to warrant action by a customer.
Update the Digital Science configuration
If you use Digital Science in your Komodo Publications Planning environment, you must install the latest Digital Science package from the Komodo Install Serviceand update your Digital Science configuration as follows:
Create a Digital Science external credential. For more information, reference 1. Create a Digital Science external credential.
Create a new Digital Science named credential. For more information, reference 2. Create a Digital Science named credential. This will replace the legacy Digital Science named credential that no longer establishes an integration with Digital Science.
Update the Default (
PP_Default) Digital Science Setting (mvn__PP_Digital_Science_Setting__mdt) metadata record to use the new Digital Science named credential. For more information, reference 3. Update the default Digital Science Setting metadata record.