Hotfixes

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 Komodo Publications Planning 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 Komodo Install Service, and Pubs API v3 will function as expected with Portal API v3.

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