The Pega Knowledge Loader

To use content that you store on a SharePoint site, you must first build a SharePoint Loader from the Pega Knowledge loader portal. The following table lists all the properties of the SharePoint loader that you must provide when you create the SharePoint Loader:

You can also choose whether the SharePoint loader should include sub-folders, and set several optional settings:

Once you are ready, click Submit to create the SharePoint loader. This creates two background jobs, the first of which runs to extracts the list of files from SharePoint, and the second to extract the files and ingest them into Knowledge Buddy or update them when needed. This happens at regular intervals, as configured in the job scheduler.

You can apply the following customizations to the Knowledge Loader to better match the needs of your organization:

1. Sourcing from any type of repository: The framework supports pulling data from repositories other than SharePoint. To use another repository, you must create a subclass in the PegaKnowledgeLoaderWorkRepository class for the new repository type. Implement the necessary Data Pages and activities to fetch files and folders from the new repository.
2. Pushing to Any Destination: By default, the framework pushes data to Knowledge Buddy, but you can extend the framework to push data to other destinations by overriding specific activities.
3. Decoding File Content: The framework uses Apache Tika by default to decode file content. However, you can use a different framework to decode the content by overriding the provided extension points.
4. Additional Attributes: The framework enables you to ingest additional custom attributes from the source repository. You can extend the data pages and activities to handle these custom attributes.
5. Job Schedulers: The Knowledge Loader includes job schedulers that periodically ingest new files and check for updates. You can customize the scheduling intervals and the logic for handling updates.