Hotfixes

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.

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.

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.

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.

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.

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.

Users are able to mute task assignment notifications on manual workflow stages by checking the Mute notifications for this workflow checkbox.

MPP-2678

Collaborator Portal versions can now be changed in sandbox environments.

Fall '24 Hotfix 1 (1.38.0.3)

MPP-2744

When the Allow Relationship Attachment (mvn__CM_Allow_Relationship_Attachments__c) field on a Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata record was unchecked but one or more files that exceeded the 25MB file limit were automatically selected, the user would not be able to advance in the Start Workflow modal because the files did not appear in the modal for the user to deselect them.

If a user is automatically assigned files that exceed the file size limit but the Allow Relationship Attachment field is unchecked, the user can continue to advance in the Start Workflow modal. If a user is automatically assigned files that exceed the file size limit and the Allow Relationship Attachment field is checked, an error message will appear and prevent the user from advancing in the Start Workflow modal until they deselect the large files.

MPP-2802

The picklists in the final screen of the Add Collaborator wizard opened behind the footer of the wizard. This meant that if there was more than one picklist option, the additional picklist options appeared to be hidden by the wizard. However, users were still able to scroll down inside the wizard to view and select the additional picklist options.

The picklists now open in front of the Add Collaborator wizard so that all of the picklist options are immediately visible to users.

Fall '24 Hotfix 2 (1.38.1.3)

MPP-2811

Document collaborators who were assigned the Viewer role on a document were unable to see the document’s package files in the Collaborator Portal. This happened when the active Portal API version was not v2, such as in the initial Scientific Publications Cloud Fall '24 release that used Portal API v3 with Pubs API v2.

A new Pubs API version (v3) has been released, and a new corresponding Pubs API Version (mvn__PP_Pubs_API_Version__mdt) metadata record that uses Pubs API v3 is available. The Pubs API Version v3 (Pubs_API_Version_v3) metadata record will be installed automatically with the hotfix through the Install Service, and Pubs API v3 will function as expected with Portal API v3.

PLTFM-3275

If a workflow had tasks of different types (e.g., one approval task and one general task), the workflow did not always transition when a user completed all of the tasks. This was because the Workflow Stage Transition (mvn__CM_Workflow_Stage_Transition__mdt) metadata record that controlled the workflow transition only checked that the workflow stage activities of one type were completed (e.g., the workflow event type equaled either AllReviewersApproved or AllTasksCompleted). However, the type of the task that was last completed in the workflow and the type of the event that was checked in the workflow stage transition did not always match (e.g., if the last completed task was an approval task but the workflow transition criteria required the AllTasksCompleted event).

Workflow transitions have been updated to account for multiple task types in a single workflow. Admin users must create a Workflow Stage Transition metadata record for each type of task in a workflow that checks for the corresponding workflow event type.

Fall '24 Hotfix 3 (1.38.1.4)

MPP-2920

Some external document collaborators who tried to log into the Collaborator Portal without a password ran into a script error on the verification page. This meant that the users would not receive a verification code in their emails and therefore could not log in without a password.

The custom Verification (PP_Verification) Visualforce page has been removed and replaced with the standard Salesforce verification page. Users will no longer run into script errors, and admin users can customize the standard "Verify Your Identity" page as desired.

Fall '24 Hotfix 4 (1.38.1.6)

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.

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.

Users are able to mute task assignment notifications on manual workflow stages by checking the Mute notifications for this workflow checkbox.

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 Hotfix 1 (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-2678

Collaborator Portal versions can now be changed in sandbox environments.

Spring '24 Hotfix 2 (1.32.0.2)

MPP-2744

When the Allow Relationship Attachment (mvn__CM_Allow_Relationship_Attachments__c) field on a Workflow Stage Activity (mvn__CM_Workflow_Stage_Activity__mdt) metadata record was unchecked but one or more files that exceeded the 25MB file limit were automatically selected, the user would not be able to advance in the Start Workflow modal because the files did not appear in the modal for the user to deselect them.

If a user is automatically assigned files that exceed the file size limit but the Allow Relationship Attachment field is unchecked, the user can continue to advance through the Start Workflow modal. If a user is automatically assigned files that exceed the file size limit and the Allow Relationship Attachment field is checked, an error message will appear and prevent the user from advancing in the Start Workflow modal until they deselect the large files.

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.

PLTFM-2410

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.

Spring '23 1.27