Fall '23 release notes

PLTFM-2409

Upon upgrading to Salesforce’s Spring ’24 release, users who tried to use the Document Collaborator Search (ppCollaboratorSearchModal) wizard to add a new document collaborator ran into an issue where the subsequent screens in the wizard never finished loading.

Users are able to progress through the Document Collaborator Search wizard and add document collaborators to documents.

Fall '23 1.28.0.19

PLTFM-2483

When a document collaborator completed a workflow task on behalf of a task assignee, the task assignee would inadvertently lose their document role(s).

Task assignees retain their document roles when other document collaborators complete workflow tasks on their behalf.

Fall '23 1.28.0.25

MPP-2401

In certain scenarios, the batch job to provision new document collaborators failed to send out the welcome email required to set up Collaborator Portal accounts, so the external users were never created. Additionally, the batch job sometimes provisioned users but failed to update the document collaborator status from Pending to Active.

When the batch job to provision new document collaborators is run, a welcome email is sent out to every user who needs to set up a Collaborator Portal account and the status for all provisioned users is set to Active.

Fall '23 1.31.0.8

MPP-2431

If a document was related to a publication plan and plan team members were configured to be automatically provisioned access to the document, duplicate document collaborators were created for some of the plan team members on the document in certain scenarios. Additionally, if an external document collaborator completed a task that initiated an auto-start workflow and the user who was assigned with the auto-start workflow task did not have the necessary document role to perform the task, a duplicate document collaborator could be created for the user to include the additional document role.

Every user and plan team member will only have one Document Collaborator (mvn__PP_Document_Author__c) record on a document. This means that if a task assignee needs an additional document role that is not yet on the document collaborator, the document role will be added to the existing Document Collaborator record for the task assignee.

MPP-1243

To prevent errors during an upgrade, admin users had to reset the Type (mvn__CM_Type__c) field on the Document Relationship (mvn__CM_Document_Relationship__c) object from the active CM_Sourced value to the default Sourced value. Then, after the upgrade, admin users had to switch the default Sourced value back to the desired CM_Sourced value as well as re-enable history tracking on the Account, Contact, and Product (mvn__CM_Product__c) objects.

enableHistory and trackHistory tags on specific SObject fields were causing field history to be reset during upgrades and have therefore been removed for all SObjects and SObject fields. The Type field on the Document Relationship object should always equal CM_Sourced and will no longer be reset to the default Sourced value.

MPP-1324

Customers had a maximum limit of 12,000 active users with the CM_User custom permission in the Collaborator Portal. If customers exceeded this limit, users would run into a Too many query rows: 50001 error when assigning and canceling workflow tasks.

Users ran into the error because the query on Komodo Publications Planning's backend that loads the appropriate permissions for the Collaborator Portal users was getting called too many times. The query has been optimized, and customers can now add more than 12,000 users to the Collaborator Portal as needed.

MPP-1680

Customers ran into errors when adding new plan team members to existing plans that had more than 5,000 documents because the PP_ExistingRolePlanTeamMemberBatchJob batch class would hit governor limits.

The PP_ExistingRolePlanTeamMemberBatchJob batch class has been converted into a Queueable Apex class that creates document collaborators and document roles on a set of documents without hitting governor limits. The code to Configure Document Collaborator and Plan Team Member automation has also been updated to use the new PP_PlanTeamMemberQueueSchedulable class.

MPP-1681

Canceled and Cancelled were redundant task statuses. The Update Canceled Tasks to Cancelled (PP_Update_Canceled_Tasks_To_Cancelled) flow was created to update unclosed Canceled tasks to closed Cancelled tasks.

The Cancelled task status has been removed and the Update Canceled Tasks to Cancelled (PP_Update_Canceled_Tasks_To_Cancelled) flow has been deprecated. Canceled tasks are closed automatically.

MPP-1892

The alternative (alt) text for the logo in system event emails always said "Mavens Komodo Health Logo," even if users changed the image via the System Event Setting (mvn__SE_System_Event_Setting__mdt) custom metadata type.

The alt text has been updated from "Mavens Komodo Health Logo" to "Logo."

MPP-1896, PLTFM-2147

The non-enhanced previewer displayed a “No preview available” message for Office 365^TM files (e.g., docx, doc, pptx, etc). This was caused by Salesforce dropping svg-based preview renditions in Hyperforce. (For more information, reference Salesforce's notice on Content file preview issues.)

Different rendition types (e.g., SVG, JPG, or thumbnail) will now be used depending on whether an org has Hyperforce or non-Hyperforce infrastructure. This ensures that file previews will always open as expected.

MPP-1964

Visualforce pages had cross-site scripting (XXS) vulnerabilities.

All URL parameters and user input handled by script tags have been encoded with JSENCODE. Visualforce pages are no longer vulnerable to cross-site scripting attacks.

MPP-2035 / PLTFM-2250

If a user checked out and modified a package file and then checked in the updated package file with the parent document, the updated package file would be associated with both the original document version and the new document version. However, the modifications in the package file should only be retained in the new document version.

Modifications to checked out package files are now only saved in the new document version when the updated package files are checked in with the parent document.

MPP-2099 / PLTFM-2290

If a Workflow Stage (mvn__CM_Workflow_Stage__mdt) metadata record had multiple Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata records whose Days to Complete Calculation (mvn__CM_Days_To_Complete_Calculation__c) field was set to Business Days and task assignees were automatically populated in the Start Workflow modal, the task due dates would be calculated with actual days instead of regional business hours. Additionally, users were unable to correct the due dates because the Business days until due and Due Date fields in the modal would be disabled. The due dates would only correct themselves if users navigated to the next screen in the modal and then back.

The due date for every task in the Start Workflow modal is now calculated according to the Days to Complete Calculation field and the selected task assignees as expected. Additionally, the fields in the modal are no longer disabled, so users can update the due dates as needed.

PLTFM-1863

If a user clicked the down arrow under a document title in the Related Documents component, the related document would open instead of the menu containing the Delete option. This meant that users were unable to delete documents from the Related Documents component.

The down arrow for each document in the Related Documents component now appears next to the document title instead of under and opens the menu with the Delete option instead of the related document. This allows users to delete documents from the Related Documents component.

PLTFM-2248

If a user set the Assignment (mvn__CM_Assignment__c) field on a Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata record to Workflow Creator, the workflow would hang on the spinner and never start.

Workflows where activities are assigned to the workflow creator no longer hang on the spinner and instead start as expected.

PLTFM-2249

If a user checked out a document that had no existing package files, another document collaborator was able to upload a single new package file to the document. Only after the first package file was uploaded would the New button in the Package Files related list become disabled for document collaborators who did not check out the parent document.

If a user checks out a document, the New button in the Package Files related list is immediately disabled for other document collaborators. Only the user who checks out the parent document is able to upload new package files.

PLTFM-2254

If a user checked out and opened a package file in Office 365^TM and then uploaded a new package file in the Package Files related list, the new package file would overwrite the checked out Office 365^TM package file.

New package files no longer overwrite existing package files. If a user checks out and opens a package file in Office 365^TM and then uploads a new package file in the Package Files related list, the new package file will appear in the related list along with the existing package file.

PLTFM-2271

If a user assigned a task via the Start Workflow modal and the Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata record was configured such that the Days to Complete Calculation (mvn__CM_Days_To_Complete_Calculation__c) field equaled Business Hours while the Role Assignment (mvn__CM_Role_Assignment__c) field was set to a role that was already on the document, the due date on the task would be calculated with actual days instead of regional business hours. The due date would only correct itself if the user hovered over the Business days until due field in the Start Workflow modal.

The due date for any task assigned via the Start Workflow modal is now calculated according to the Days to Complete Calculation field on the Workflow Stage Activity custom metadata type as expected.

PLTFM-2284

The due date for the first task in an auto-start workflow was always calculated with actual days, even if the Days to Complete Calculation (mvn__CM_Days_To_Complete_Calculation__c) field on the Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata record was configured to use regional business hours.

The due date for every task in auto-start workflows is now calculated according to the Days to Complete Calculation field on the Workflow Stage Activity custom metadata type as expected.

PLTFM-2298

Users were unable to complete tasks on behalf of other users and instead received error messages like "Update failed... Insufficient access rights on object...", even if the Complete Tasks on Behalf of Other Users (mvn__CM_Task_Completion_On_Behalf_Of_Enabled__c) field on the MCM Global Setting (mvn__CM_Global_Setting__mdt) custom metadata type was checked and the users had all the necessary permissions.

Users are now able to complete tasks on behalf of other users without encountering any error messages.

PLTFM-1530

mvn__CA_Office_365_Setting__mdt

mvn__CA_API_Version__c

API version used to build the Office 365™ endpoint URL.

MPP-1681

PP_Update_Canceled_Tasks_To_Cancelled

Updated non-closed Canceled tasks to closed Cancelled tasks.