Spring '24 release notes

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.

Spring '24 1.32.0.1

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-2090, PLTFM-2243

AuraHandlerException, the Apex exception class required to throw errors for Aura components, obscured errors in Lightning Web Components (LWCs). This caused "Script-thrown exception" to be the only error message to appear for LWC errors, which could be vague and confusing for users.

AuraHandlerException is removed for LWCs and users are able to see more relevant and informative error messages for errors in LWCs.

MPP-2101

For each publication in the Collaborator Portal, the Open in Office 365 button in the Download History tab downloaded document versions locally to the user's computer instead of opening the document versions in Office 365™.

The button has been renamed from "Open in Office 365" to "Download".

MPP-2121

Users who tried to view an Office 365™ document or who tried to open the Check Out Document modal for an Office 365™ document sometimes ran into a "List index out of bounds: 0" error message. This list exception error occurred when the Office 365™ integration was misconfigured because it assumed that an Office 365 Setting (mvn__CA_Office_365_Setting__mdt) metadata record exists.

The Office 365™ integration now checks to make sure an Office 365 Setting metadata record exists so that the list exception error no longer appears. If the Office 365™ integration is misconfigured and is missing an Office 365 Setting metadata record, users are not be able to check out the document in Office 365™.

MPP-2122

File formats for workflow attachments were not getting captured correctly.

Additional file mappings are provided out of the box to ensure that file formats for workflow attachments are captured correctly. For the list of file mappings that have been added, reference Table 36, “Modified custom metadata records”.

MPP-2123

When workflow tasks with attachments were assigned to more than one user, only the first user on the task would receive the attachments.

Every user assigned to workflow tasks with attachments will receive the attachments on the tasks.

MPP-2144

Users who tried to view archived Task records ran into an “Attempt to de-reference a null object” error message.

Archived Task records can now be viewed without errors.

MPP-2237

Out of the box, Komodo Publications Planning provided two email builders, PP_TaskNotificationEmailBuilder and PP_EmailBuilder, that had similar functionality.

The two email builders have been merged so that PP_EmailBuilder contains all of the functionality required to send out emails. PP_TaskNotificationEmailBuilder has subsequently been deprecated.

MPP-2291

When users assigned a workflow task, the task assignee would receive a notification about the task. However, when users reassigned the workflow task, the new task assignee would not receive any notifications.

Notifications will be sent to the new task assignee when a workflow task is reassigned.

PLTFM-2063

When users clicked on a picklist field, hovered over the options, and then clicked out of the field and dropdown, the dropdown remained expanded. This caused multiple picklist dropdowns to be open at the same time. The dropdowns only closed if the users selected a picklist option or if the users never hovered over any of the picklist options.

Picklist dropdowns now close when users move their mouse anywhere outside of the picklist field and dropdown. This means that only one picklist dropdown can be open at a time.

PLTFM-2241

The Severity (mvn__Severity__c) field on the Debug Log (mvn__Debug_Log__c) object was missing several log levels.

Additional log levels have been added as picklist values to the Severity field on the Debug Log object.

PLTFM-2462

When workflow tasks were assigned to 40 or more users, Komodo Publications Planning hit SOQL query limits and a "Too many SOQL queries" error message appeared.

Assigning workflow tasks to 40 or more users no longer hits SOQL query limits. The performance of adding multiple attachments to tasks with multiple users has also been improved.

PLTFM-2472

When users selected one or more related document files in the Start Workflow modal to be sent to external task assignees, the files were not always attached to the workflow task email notifications.

External document collaborators will receive all the selected file attachments in their workflow task email notifications.

PLTFM-2549

The Manage Sharing (CM_Manage_Sharing) Permission (mvn__CM_Permission__mdt) metadata record determines which users can manage and modify document collaborator roles on a document. However, users who did not have the Manage Sharing document permission were able to delete document collaborator roles from a document.

Only users who have the Manage Sharing document permission are able to manage (e.g., delete) the roles of document collaborators on a document.

MPP-2237

PP_TaskNotificationEmailBuilder