Hello, I wanted to check if anyone has implemented or worked with the Pulse → External Sources feature using the Pega Cloud Repository instead of SharePoint or another external repository.
Based on the PDN resources, I found examples of integrating External Sources with SharePoint. However, in our case, the configuration points to the Pega Cloud Repository. I’d like to understand the underlying architecture and how this integration is expected to work with the Pega Cloud Repository.
Has anyone implemented this use case or can share their experience with it?
I also observed that opening External Sources takes some time to load, almost as if the application is retrieving all available records from the repository before rendering the screen. During this time, the Submit button remains grayed out until the loading completes.
I haven’t come across a production implementation where External Sources was explicitly configured to use the Pega Cloud Repository in the same way as SharePoint or OneDrive. Most examples and customer implementations use external document management systems (SharePoint, CMIS, Box, etc.) because the feature was primarily designed for sourcing existing enterprise documents rather than browsing Pega-managed storage.
Here’s what is likely happening behind the scenes:
Pulse invokes the Repository API to retrieve the list of files/folders from the configured repository.
The Pega Cloud Repository is simply another implementation of the Repository API (similar to S3, Azure Blob, etc.), so from the UI’s perspective it is just another repository provider.
Unlike SharePoint integrations, there isn’t any special indexing or search service exposed to Pulse. The UI generally relies on repository list operations to populate the file browser hence the slow loading.
