Spring '25 release notes

A new Timeline (khvTimelineWrapper) component is available to provide an enhanced timeline visualization in the form of a Gantt chart. It 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 existing Timeline (ppTimelineWrapper) component. A default configuration for the enhanced timeline visualization can also be deployed via the Komodo Install Service to show related journals and congresses on annual plans. To use this, admin users can drag and drop the new Timeline component onto any Annual Plan (mvn__PP_Plan_Budget__c) flexipage.

Related work item(s): MPP-2149, MPP-2150, MPP-2349, MPP-2350, MPP-2351, MPP-2352, MPP-2353, MPP-2383, MPP-2384, MPP-2444, MPP-2448, MPP-2453, MPP-2462, MPP-2481, MPP-2482, MPP-2504, MPP-2542, MPP-2543, MPP-2798, MPP-2799, MPP-2800, MPP-2801, MPP-2870

An integration with Google Drive is now available through Salesforce's Files Connect service to enable users to create, reference, and collaborate on files that are hosted externally. The files can be Microsoft 365 files, Google Drive files, and other text and image files stored in Google Drive. Users can use this feature to create both documents and package files in Komodo Publications Planning and can create snapshots of the files to track changes. The free, default Files Connect integration uses Google Drive as an external data source and enforces a file size limit of 6MB while the premium Files Connect integration uses Google Drive as an external service and can upload files up to 75MB and download files up to 2GB per Salesforce's limitations.

Related work item(s): PLTFM-3034, PLTFM-3037, PLTFM-3075, PLTFM-3096, PLTFM-3107, PLTFM-3108, PLTFM-3109, PLTFM-3116, PLTFM-3127, PLTFM-3136, PLTFM-3149, PLTFM-3162, PLTFM-3168, PLTFM-3169, PLTFM-3170, PLTFM-3173, PLTFM-3193, PLTFM-3201, PLTFM-3300

Trigger Action Framework (TAF) is a new feature that allows developers and administrators to configure trigger logic with custom metadata, including turning trigger functions on and off as well as managing the order in which each trigger runs. The framework can be used with both Apex classes and flows and works for both Komodo Publications Planning code and custom code. With TAF, there is a new global Apex class that can be called and three new custom metadata types. The Trigger Action (mvn__TAF_Trigger_Action__mdt) custom metadata type defines an individual trigger or action to run and when, the sObject Trigger Setting (mvn__TAF_sObject_Trigger_Setting__mdt) custom metadata type defines the sObject and context in which the trigger or action should run, and the Trigger Finalizer (mvn__TAF_DML_Finalizer__mdt) custom metadata type defines the final piece of code that should execute once at the end of a Data Manipulation Language (DML) operation. For product documentation, including configuration steps, reference Trigger Action Framework.

Related work item(s): MPP-2828

Komodo Publications Planning has a sync service that ensures related Document (mvn__CM_Document__c) records, such as Document Version (mvn__CM_Document_Version__c) records, Document Collaborator (mvn__PP_Document_Author__c) records, and Document Role (mvn__CM_Document_Role__c) records, are all in sync. For example, if a document collaborator is set to inactive, the sync service ensures that all of their document roles are removed. In previous versions of Komodo Publications Planning, the sync service was in a queueable class and was triggered from record updates. In the Spring '25 release, the sync service is moved into the new PP_DocumentRoleCollaboratorSyncBatchable and PP_DocumentRoleCollabSyncSchedulable classes and is triggered via the Trigger Action Framework (TAF) described above. This update reduces the reliance on multiple Queueable jobs, streamlining sync operations and improving data integrity. When triggered, the new Pending Sharing Update (mvn__CM_Pending_Sharing_Update__c) field on the Document record is set to true, a warning message appears on the Document Collaborators related list to indicate that a sync is pending or in process, and the scheduled batch class retrieves all of the pending documents and sync any related records, including populating the Annual Plan (mvn__PP_Plan_Budget__c), Concept (mvn__PP_Concept__c), DOI (mvn__PP_DOI__c), and Publication Plan (mvn__PP_Plan__c) fields on the appropriate Document Version record(s). The batch class is scheduled to run every 5 minutes by default.

Related work item(s): MPP-2689, MPP-2919

When a document was cloned in previous versions of Komodo Publications Planning, none of the document collaborators from the original document appeared in the Document Collaborators component on the cloned document. In the Spring '25 release, all of the document collaborators from the original document are propagated onto the cloned document, and admin users can specify the set of fields on the Document Collaborator (mvn__PP_Document_Author__c) object that should be copied over. A new Cloned From (mvn__CM_Cloned_From__c) field is also available on the Document (mvn__CM_Document__c) object to track the original document from which the current document was cloned.

Related work item(s): MPP-2829, PLTFM-3276

New fields on the MCM Global Setting (mvn__CM_Global_Setting__mdt) custom metadata type are available to hide each of the file hosting options in the New Document wizard. This enables admin users to have greater control over the types of documents that users can create in Komodo Publications Planning.

Related work item(s): PLTFM-3034, PLTFM-3094

Any custom workflow outcomes that are configured for the Salesforce instance of Komodo Publications Planning to more accurately capture the statuses of workflows and tasks will also appear in the Collaborator Portal. This means that users in both the Salesforce instance and the Collaborator Portal can select from the same custom options when marking a workflow task complete. When no custom outcomes are set, the Task record type continues to be used for the possible workflow outcomes in the Collaborator Portal, as in previous releases. 

Related work item(s): MPP-2565, MPP-2566

If the integration with Google Drive through Salesforce's Files Connect service is configured as described above, any external documents or files that are created in the Salesforce instance of Komodo Publications Planning will appear in the My Publications tab in the Collaborator Portal. However, Collaborator Portal users will only be able to view the documents' metadata and cannot open or view the actual files. Additionally, only the package files for the external documents can be downloaded; the document files themselves cannot be downloaded.

Related work item(s): MPP-2688, MPP-2757

Two new custom labels are available in Komodo Publications Planning for admin users to configure the package file labels in the Collaborator Portal. The new PP_Pub_And_Package_File_Download_Button custom label can be used to change the default Pub & Package Files button that downloads the publication document along with any package files while the PP_Package_Files_List_Header custom label can be used to change the default "Package Files" section header within the Related Documents tab.

Related work item(s): MPP-2742

Lightning Web Security (LWS) must be enabled to install and upgrade to the Komodo Publications Planning Spring '25 release. For instructions, reference Salesforce's documentation on how to Enable Lightning Web Security in an Org.

With the introduction of the Trigger Action Framework (TAF), the ContentDocumentLink_Portal_Sharing trigger action must be enabled to ensure that users can continue to view and download document files and package files in the Collaborator Portal. To enable the ContentDocumentLink_Portal_Sharing trigger action:

If the ContentDocumentLink_Portal_Sharing trigger action is left as is and is not enabled upon the upgrade to the Spring '25 release, the trigger action will still run, just without the PP_ContentDocEnablePortalSharing Apex class installed, and subsequently throw an installation error. This is due to a Salesforce issue.

With the introduction of the Trigger Action Framework (TAF), the Contact Verification: Create Task flow must be updated to ensure that the the latest document version is stamped before the tasks are created and the contact verification emails are sent. To update the Contact Verification: Create Task flow, you can either:

With the updated sync service, read and write access must be granted for the following new Document (mvn__CM_Document__c) fields to ensure that roles are created properly when document collaborators are propagated onto cloned documents:

With the updated sync service, the following job must be scheduled to ensure that related Document (mvn__CM_Document__c) records, such as Document Version (mvn__CM_Document_Version__c) records, Document Collaborator (mvn__PP_Document_Author__c) records, and Document Role (mvn__CM_Document_Role__c) records, are all in sync:

System.schedule('PP_Process_PendingDocuments 00', '0 0 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 05', '0 05 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 10', '0 10 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 15', '0 15 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 20', '0 20 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 25', '0 25 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 30', '0 30 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 35', '0 35 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 40', '0 40 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 45', '0 45 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 50', '0 50 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));
System.schedule('PP_Process_PendingDocuments 55', '0 55 * * * ?', new mvn.PP_DocumentRoleCollabSyncSchedulable(5));