Spring '25 release notes
This topic contains the release notes for the Spring '25 release of Scientific Publications Cloud product. The release notes are organized into these high-level sections:
-
Installation and upgrades - link to install and/or upgrade to Spring '25.
-
New features - new features and functionalities in Spring '25.
-
Updated features - updated features and functionalities in Spring '25.
-
Collaborator Portal updates - updated features and functionalities in the Collaborator Portal.
-
Hotfixes - defects identified in the original Spring '25 release that were fixed via hotfix patches.
-
Defect fixes and maintenance - defects and maintenance items fixed in Spring '25.
-
Metadata changes - changes to the underlying data models, user permissions, or system configurations in Spring '25.
-
Required pre-install and pre-upgrade actions - required actions administrators must take before installing or upgrading to Spring '25.
-
Required post-upgrade actions - required actions administrators must take after upgrading to Spring '25.
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 referencing static versions of the page.
Installation and upgrades
The Scientific Publications Cloud product Spring '25 release can be installed with the Install Service at https://install.komodohealth.com/products/kpp/2.5.0.4. New installs of Scientific Publications Cloud product will be on the latest release while current customers will need to run and deploy the latest update.
Warning! Remember to complete the steps in the Required pre-install and pre-upgrade actions and Required post-upgrade actions sections below as appropriate.
New features
The new release of Scientific Publications Cloud product contains several new features whose functionalities are detailed below. Details about enablement and configuration are included within the product documentation.
Enhanced timeline visualization
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
The new release of Scientific Publications Cloud product also includes a new version of the Collaborator
therefore be used in place of 's existing Timeline
(ppTimelineWrapper) component. A default configuration for the
enhanced timeline visualization can also be deployed via the 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.
Note: If you have previously installed the Beta version of the enhanced timeline visualization, the Scientific Publications Cloud Spring '25 release contains a few enhancements, including, but not limited to, the following:
- Admin users will be able to customize the appearance of the timeline visualization by uploading a CSS file and any media files as static resources and referencing them on the Gantt Chart (
mvn__KHV_Gantt_Chart__mdt) custom metadata type.- Admin users will be able to configure filter options to be used on the timeline visualization via the Gantt Chart Item (
mvn__KHV_Gantt_Chart_Item__mdt) custom metadata type.- Users will be able to click the groups, nested groups, and subnested groups on the left column of the timeline visualization to open the linked record in a new tab.
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
Files Connect with Google Drive
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 Scientific Publications Cloud 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)
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 Scientific Publications Cloud 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.
Warning! Several default Trigger Action and Trigger sObject Setting metadata records can be deployed via the . However, if you are upgrading from a previous Scientific Publications Cloud version to the Spring '25 release, you must complete the steps in the Required post-upgrade actions section below.
Related work item(s): MPP-2828
Updated features
The new release of Scientific Publications Cloud product 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 sync service
Scientific Publications Cloud product 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 Scientific Publications Cloud product, 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.
Warning! This will be "on" by default for existing customers, and no steps are required to enable this enhancement. However, if you are upgrading from a previous Scientific Publications Cloud version to the Spring '25 release, you must complete the steps in the Required post-upgrade actions section below.
Related work item(s): MPP-2689, MPP-2919
Propagation of document collaborators onto cloned documents
When a document was cloned in previous versions of Scientific Publications Cloud product, 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.
Warning! If you are upgrading from a previous Scientific Publications Cloud version to the Spring '25 release, you must complete the steps in the Required post-upgrade actions section below.
Related work item(s): MPP-2829, PLTFM-3276
Hide file hosting options in New Document wizard
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 Scientific Publications Cloud product.
Related work item(s): PLTFM-3034, PLTFM-3094
Collaborator Portal updates
The new release of Scientific Publications Cloud product 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.
Custom workflow outcomes
Any custom workflow outcomes that are configured for the Salesforce instance of Scientific Publications Cloud 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.
Note: This will be "on" by default for existing customers, and no steps are required to enable this enhancement.
Related work item(s): MPP-2565, MPP-2566
External documents and files from Google Drive
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 Scientific Publications Cloud 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.
Note: This will be "on" by default for existing customers, and no steps are required to enable this enhancement.
Related work item(s): MPP-2688, MPP-2757
Configure package file labels
Two new custom labels are available in Scientific Publications Cloud 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.
Note: This will be "on" by default for existing customers, and no steps are required to enable this enhancement.
Related work item(s): MPP-2742
Hotfixes
The following table details defects identified in Scientific Publications Cloud Spring '25 that were fixed via a hotfix patch. You may click the links in the "Version fixed" column to install the hotfix with the .
Hotfix items
| Work item | Description | New behavior | Version affected | Version fixed |
|---|---|---|---|---|
| MPP-3037 | When the Subject (mvn__CM_Subject__c) value on a Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata record was too long, the Version Details component would try to fit as many characters from the subject as it could and inadvertently cause the filter option to disappear. | The Version Details component truncates long task subjects so that the filter option always remains visible. | Spring '25 (2.3.0.19) | Spring '25 Hotfix (2.4.0.5) |
| MPP-3052 | When tasks of manual workflow stages were assigned with attachments, the task assignment email notifications were sent out without the attachments. This was because no Workflow Instance Activity Content (mvn__CM_Workflow_Instance_Activity_Content__c) records were created for the related attachments. Note: This issue was previously identified in KI-142. | Workflow Instance Activity Content records are created for any attachments added to the tasks of manual workflow stages so that the task assignment email notifications contain the attached files as expected. | ||
| MPP-3065 | When a document group had multiple document roles, the sync service failed during pending updates. This was because the sync service only checked for updates on users and did not check for updates on document groups. As a result, the sync service created duplicate new document collaborators for document groups that had more than one document role. Note: This issue was previously identified in KI-140. | The sync service now checks for updates on both users and document groups and no longer fails when a document group has multiple document roles. | ||
| MPP-3095 | When an active document was updated and moved into a different state (e.g., from "Draft" to "In Review"), the document was erroneously flagged as inactive. As a result, Collaborator Portal users were only able to find the document under Inactive Publications in the My Publications tab. Note: This issue was previously identified in KI-144. | The new PP_DocumentVersionUpdateActiveFlag global Apex class and Document Version Sync (Document_Version_Sync) Trigger Action (mvn__TAF_Trigger_Action__mdt) metadata record ensure that every document version is properly flagged as either active or inactive and synced with its parent document. | Spring '25 Hotfix 2 (2.5.0.4) | |
| MPP-3096 | When a user tried to clone a document that they did not have the Owner role on, an error was thrown and the cloning process failed. Note: This issue was previously identified in KI-145. | Users can clone documents that they are not the record owners for. If the feature for propagating document collaborators onto cloned documents is enabled, then all of the document collaborators from the original document will be propagated onto the cloned document, except for the original document owner. | ||
| PLTFM-3437 | When manual workflow stages had multiple tasks and some of the tasks were assigned with attachments, every task assignment email notification would include the attachments, even the tasks that were not assigned with attachments. Note: This issue was previously identified in KI-143. | Email notifications of workflow task assignments only include the attachments that were selected for the specific workflow task. | Spring '25 Hotfix 2 (2.5.0.4) & Fall '24 Hotfix 5 (1.38.2.3) | |
| PLTFM-3438 | When a user tried to mute the notifications for tasks on manual workflow stages, notifications would still be sent to task assignees because the Mute notifications for this workflow checkbox in the Start Workflow modal did not function as expected. Note: This issue was previously identified in KI-141. | Users are able to mute task assignment notifications on manual workflow stages by checking the Mute notifications for this workflow checkbox. |
Defect fixes and maintenance
The following table details defects and maintenance items identified in Scientific Publications Cloud Fall '24 that are fixed in Scientific Publications Cloud Spring '25.
Fixed items
| Work item(s) | Description | New behavior |
|---|---|---|
| MPP-2368 | When a user clicked the Reset button in the Document Collaborator Search wizard, the Collaborator Type field did not reset or clear. | The Reset button in the Document Collaborator Search wizard reverts all of the search fields to their default values, including the Collaborator Type field. |
| MPP-2632, MPP-2942 | When a user clicked the Provision User button in the Document Collaborators component, the Provision User modal that opened may have appeared to load indefinitely. The user could either close out of the modal and/or refresh the page to try again or click the + Provision User button in the empty modal. However, if the user clicked the + Provision User button while the Provision User modal was still loading, the User JSON Definition (mvn__PP_User_JSON_Definition__c) field on the User Request (mvn__PP_User_Request__c) record would either be empty or incomplete. | The Provision User modal no longer loads indefinitely, and the + Provision User button in the modal is disabled (i.e., greyed out) while the modal loads. This ensures that users can only submit provision requests that contain all of the new user's information. |
| MPP-2722 | When a user created a publication plan, the user became the owner of the publication plan and no other plan team member could be added with the plan owner role. However, if a plan team member was added with another role, the role could be edited to the plan owner role. | Only one plan owner can exist on any publication plan. A new validation rule, PP_Limit_Plan_Owner, throws an error if a plan owner already exists on a publication plan and a user tries to update the role of another plan team member to the plan owner role. |
| MPP-2786 | An existing user, such as a publication manager, may have clicked the Provision User button in the Document Collaborators component multiple times for a new user because it was not always obvious if a provisioning request was already created. However, if the Provision User button was clicked more than once before the provisioning process was complete, the new user could have been created without a link to the appropriate Contact record and therefore not had access to any publications. This may have caused the publication manager to assume the new user has not yet been provisioned and click the Provision User button again. | The Provision User button is disabled (i.e., greyed out) after the provisioning request for the new user is submitted and remains disabled while the provisioning process is pending or running. This ensures that only one user request is created for each new user or contact. Existing users like publication managers will only be able to click the Provision User button again for the same new user if the initial user provisioning request fails. |
| MPP-2851 | To transfer the Owner role from the current owner of a document to another user, users had to click the down arrow next to the current document owner in the Document Collaborators component and then select the Transfer Ownership option. This user flow was not intuitive because the Transfer Ownership option was difficult to find. | A new Transfer Ownership button is added to the top right corner of the Document Collaborators component, next to the New button. This is easier to find than the original Transfer Ownership button, but the original button is still be available as well. Both buttons open the same Transfer Ownership wizard. |
| PLTFM-2551 | If a user created a document without a file and then uploaded a rendition for the document, the document's metadata appeared in both the Preview and Details tabs on the Document record page. Additionally, in the Preview tab, the document's metadata appeared below the file preview and therefore overflowed outside the file preview component. | If a document has a rendition, the Preview tab only shows the file preview and does not show the document's metadata. The document's metadata only appears in the Details tab. |
| PLTFM-3034 | When the Allow Relationship Attachments (mvn__CM_Allow_Relationship_Attachments__c) field on the Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) custom metadata type is checked, an Attachments table appears in the Start Workflow modal. This table lets users select related documents to be attached to the email notifications that are sent out to the task assignee(s). However, the table included related Document records that do not have files, and when users selected these empty related documents, an "Insert failed" error message appeared because the email cannot attach empty or non-existent files. | Related Document records that do not have files will not appear in the Attachments table in the Start Workflow modal, but an "External files can not be sent as attachments on emails and were removed from the table below" warning message will appear instead. |
| PLTFM-3072 | Document roles could not be removed from users with open workflow tasks on documents, even if the document roles were not associated to the open tasks. | Document roles can be removed from a user as long as the document roles are not associated to any of the user's open tasks on the document or the user is assigned the new CM Delete Document Role With Open Tasks (CM_Delete_Document_Role_With_Open_Tasks) custom permission. |
| PLTFM-3097 | In the Upload New Version modal, users were able to create a new version of a document without uploading a file. | The Upload New Version modal requires a file to be uploaded for every new document version. If users click Save without uploading a file, an error message appears. |
| PLTFM-3324 | NotIncludes was not a valid operator value in criteria definitions. | Users can set the operator property to equal NotIncludes when creating criteria definitions. |
Metadata changes
The following subsections capture the changes against entities in key areas of Scientific Publications Cloud 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(s) below:
New Apex classes
| Work item(s) | Apex class |
|---|---|
| MPP-2689 | PP_DocumentRoleCollaboratorSyncBatchable PP_ResetPasswordRequestService PP_DocumentRoleCollabSyncSchedulable PP_DocumentRoleCollabSyncSchedulable |
| MPP-2828 | TAF_DynamicTriggerHdlr |
| MPP-3095 | PP_DocumentVersionUpdateActiveFlag |
Aura components
Aura component changes are listed in the table(s) below:
New Aura components
| Work item(s) | Aura component |
|---|---|
| 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 | khvTimelineWrapper |
Custom labels
Custom label changes are listed in the table(s) below:
New custom labels
| Work item(s) | Custom label(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 | KHV_Gantt_Chart_Not_Found KHV_Item_Due_Date_Status_Approaching_Deadline KHV_Item_Due_Date_Status_In_Progress KHV_Item_Due_Date_Status_Overdue KHV_Item_Due_Date_Status_Today KHV_Query_Misconfiguration KHV_Timeline_Header |
| MPP-2742 | PP_Package_Files_List_Header PP_Pub_And_Package_File_Download_Button |
| MPP-2919 | PP_Document_Collaborator_List_Header_Subtitle PP_Document_Collaborator_List_Header_Subtitle_Helptext |
| PLTFM-3034, PLTFM-3037, PLTFM-3075, PLTFM-3096, PLTFM-3108, PLTFM-3109, PLTFM-3116, PLTFM-3127, PLTFM-3162, PLTFM-3169, PLTFM-3173, PLTFM-3193, PLTFM-3201, PLTFM-3300 | CM_Add_File_No_Options_Instructions CM_Authorize_File_External_Service CM_Authorize_File_Repository CM_Can_Not_Replace_Existing_File CM_Copy_Link CM_Create_Snapshot_Version CM_Document_New_Version_Snapshot_Email_Body CM_Document_New_Version_Snapshot_Feed_Body CM_Document_New_Version_Snapshot_Notification_Body CM_Document_Version_Can_Not_Replace_File CM_Document_Version_No_Folder_Message CM_Document_Version_Snapshot_Log CM_External_File_Warning CM_File_Create_Type_Not_Supported CM_File_External_Auth_Close_Message CM_File_No_Options CM_File_Repository_Auth_Close_Message CM_File_Repository_Auth_Close_Title CM_File_Repository_Back CM_File_Repository_Create CM_File_Repository_Create_New CM_File_Repository_Loading_More CM_File_Repository_New_Item CM_File_Repository_Select CM_File_Repository_Select_File CM_File_Repository_Select_Folder CM_File_Size_Limit_Exceeded CM_Files_Connect CM_Files_Connect_Disclaimer CM_Files_Connect_Document CM_Files_Connect_Presentation CM_Files_Connect_Spreadsheet CM_Files_Connect_Upload_File CM_Latest_External_File_Warning CM_Latest_External_File_Warning_Header CM_Microsoft_Excel CM_Microsoft_PowerPoint CM_Microsoft_Word CM_Missing_File_Repository_Permissions CM_Missing_Files_Connect_File_Access CM_New_External_Version CM_New_Snapshot_Version CM_No_Repositories CM_Open CM_Package_File_Queue_Success_Message CM_Replace_Existing_File CM_Replace_File CM_Search_File_Repository CM_Select_From_File_Repository CM_Selected_File CM_Selected_Folder CM_Service_File_Size_Limit_Exceeded CM_Snapshot_Current_Version CM_Snapshot_File_Size_Limit_Exceeded CM_Snapshot_Queue_Success_Message CM_System_Event_Document_New_Version_Snapshot CM_Upload_External_Version CM_Upload_New_File |
| PLTFM-3097 | CM_Document_Version_No_File_Message |
Modified custom labels
| Work item(s) | Custom label | Modification description |
|---|---|---|
| PLTFM-3169 | CM_Upload_New_Version | Value was updated from Upload New Version to Create New Version. |
| PLTFM-3300 | CM_Add_File_Instructions | Value was updated from To add a file use the Upload File or Add External Link buttons above to To add a file use the buttons above. |
Custom metadata types
Custom metadata type changes are listed in the table(s) below:
New custom metadata types
| Work item(s) | Custom metadata type(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 | mvn__KHV_Gantt_Chart__mdt mvn__KHV_Gantt_Chart_Item__mdt |
| MPP-2828 | mvn__TAF_Trigger_Action__mdt mvn__TAF_DML_Finalizer__mdt mvn__TAF_sObject_Trigger_Setting__mdt |
New custom metadata fields
| Work item(s) | Custom metadata type | Field(s) |
|---|---|---|
| MPP-2829 | mvn__PP_Global_Setting__mdt | mvn__PP_Cloned_Doc_Collab_Field_Set_Name__c mvn__PP_Doc_Collaborator_Propagation_on_Clone__c |
| PLTFM-3034, PLTFM-3094, PLTFM-3116, PLTFM-3127, PLTFM-3169, PLTFM-3173 | mvn__CM_Global_Setting__mdt | mvn__CM_Enable_External_Files_Connect__c mvn__CM_Files_Connect_Environment__c mvn__CM_Files_Connect_Excel_Template__c mvn__CM_Files_Connect_Snapshot_To_Current__c mvn__CM_Files_Connect_PowerPoint_Template__c mvn__CM_Files_Connect_Word_Template__c mvn__CM_Hide_External_File_Button__c mvn__CM_Hide_Files_Connect_File_Button__c mvn__CM_Hide_M365_File_Button__c mvn__CM_Hide_No_File_Button__c mvn__CM_Hide_Translation_File_Button__c mvn__CM_Hide_Upload_File_Button__c |
New custom metadata records
| Work item | Custom metadata type | Metadata record name(s) |
|---|---|---|
| MPP-3095 | mvn__TAF_Trigger_Action__mdt | Document_Version_Sync |
| PLTFM-3034, PLTFM-3109 | mvn__SE_System_Event__mdt | CM_Document_New_Version_Snapshot |
| mvn__SE_System_Event_Configuration__mdt | CM_Document_New_Version_Snapshot | |
| PLTFM-3034, PLTFM-3149 | mvn__CT_Content_Type__mdt | bmp gif jpg png svg tiff zip |
Modified custom metadata fields
| Work item(s) | Custom metadata type | Field | Modification description |
|---|---|---|---|
| PLTFM-3034, PLTFM-3109 | mvn__CM_Document_State_Entry_Action__mdt | mvn__CM_Type__c | Added the New Snapshot Version (CM_New_Snapshot) picklist value. |
Objects
Object changes are listed in the table(s) below:
New object fields
| Work item(s) | Object | Field |
|---|---|---|
| MPP-2689 | mvn__CM_Document__c | mvn__CM_Pending_Sharing_Update__c |
| MPP-2799, MPP-2801 | mvn__PP_Milestone__c | mvn__PP_Due_Date_Status__c mvn__PP_Formatted_Name__c |
| MPP-2829 | mvn__CM_Document__c | mvn__CM_Cloned_From__c |
| PLTFM-3034, PLTFM-3168 | mvn__CM_Document__c | mvn__CM_External_Content_Version_Id__c |
Modified object fields
| Work item(s) | Object | Field | Modification description |
|---|---|---|---|
| PLTFM-3169 | mvn__CM_Document_Version__c | mvn__CM_Check_Out_Type__c | Added FilesConnect as a picklist value. |
New object field sets
| Work item(s) | Object | Field set |
|---|---|---|
| MPP-2829 | mvn__PP_Document_Author__c | mvn__PP_Document_Author_Clone_Fields |
Permissions
Permission changes are listed in the table(s) below:
New custom permissions
| Work item | Custom permission |
|---|---|
| PLTFM-3072 | CM_Delete_Document_Role_With_Open_Tasks |
Static resources
Static resource changes are listed in the table(s) below:
New static resources
| Work item(s) | Static resource(s) |
|---|---|
| MPP-2757, PLTFM-3034, PLTFM-3116 | cmExcelTemplate cmPowerPointTemplate cmWordTemplate |
Required pre-install and pre-upgrade actions
This section includes the required actions administrators must take before installing and upgrading to the Scientific Publications Cloud Spring '25 release.
Enable Lightning Web Security
Lightning Web Security (LWS) must be enabled to install and upgrade to the Scientific Publications Cloud Spring '25 release. For instructions, reference Salesforce's documentation on how to Enable Lightning Web Security in an Org.
Required post-upgrade actions
This section includes the required actions administrators must take after upgrading to the Scientific Publications Cloud Spring '25 release. Each required action specifies the criteria for consideration, which details the conditions that must exist to warrant action by a customer.
Update the Contact Verification: Create Task flow
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:
-
Deploy the unpackaged setup metadata via the ; or
-
Update the flow manually:
-
In Setup, search for and select Flows.
-
Select the Contact Verification: Create Task flow.
-
Before the "Is Background Check?" step, add a 3-minute delay.
-
Save the changes.
-
Grant read/write access for new Document fields
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:
-
Cloned From (
mvn__CM_Cloned_From__c) -
Pending Sharing Update (
mvn__CM_Pending_Sharing_Update__c)
Schedule document collaborator sync job
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));