Skip to main content

KI-136

Package files don’t appear in the Collaborator Portal

Created date	01/21/2025	Updated date	01/21/2025
Status	Done	Related work item	MPP-2811
Description	External document collaborators who are assigned the Viewer role on a document are unable to see the document’s package files in the Collaborator Portal. This happens when the version of the Portal API that is being used is not v2, such as in Komodo Publications Planning Fall '24 when the Portal API is automatically set to v3 on install.
Affects version(s)	Fall '24	Impacted capabilities	N/A
Steps to reproduce	Prerequisites: You must use Portal API v3 in your Salesforce environment. This is installed and configured automatically with Komodo Publications Planning Fall '24. You must have a Collaborator Portal associated with your Salesforce environment. For instructions on how to set up and configure a Collaborator Portal, reference Collaborator Portal. Steps: Log into your Salesforce environment. Open a new or existing Document record. The document should be related to an active publication plan. Create a package file for the document. Add an external document collaborator with the Viewer role to the document. Log into the Collaborator Portal as the external document collaborator. Open the publication plan. Click the Related Documents tab. Notice how the package file that was added to the document in the Salesforce environment does not appear in the Collaborator Portal.
Workaround	In Setup, navigate to the Pubs API Version (`mvn__PP_Pubs_API_Version__mdt`) custom metadata type. On the Pubs API Version metadata record whose Is Active? (`mvn__PP_isActive__c`) field is `true`: Change the Portal API Version (`mvn__PP_Portal_API_Version__c`) field from `v3` to `v2`. Confirm that the Pubs API Version (`mvn__PP_Pubs_API_Version__c`) field equals `v2`.
Fix version	Fall '24 Hotfix 2 (1.38.1.3)	Resolution notes	Fix version can be installed through the Komodo Install Service.