Importing/Associating Sharepoint Articles into Pega Knowledge Management
We have a customer that currently uses SharePoint to house all their knowledge articles. We are able to link to external URL's in Knowledge Management, but is there a way to create linkages w/o having to manually input an associated article in KM.
***Edited by Moderator Marissa to update platform capability tags***
HI Scott,
Thank you for the above information it is very helpful ..
Our business is facing another issue after importing a content ..
Issue description:
When an author is trying to import an article through .CSV file and adding the content with Source data..They could able to import successfully but the font is causing issues..it is not correctly imported like font is not same as imported content and after user tries to edit , fix and save, preview and content description is not showing correct and expecting format..
it is little concerned because the font is not consistent through out the document like some headers are showing in bold while others are not.
It will really great if you could provide any help on this..please feel free to ask any other information you are looking for..
Thanks in advance..
Two options to avoid manual creation of corresponding Pega Knowledge articles:
1) Use the Pega Knowledge bulk import (.csv file) feature to pre-load all of the targeted Sharepoint articles, assuming they each have unique absolute URL's. In the .CSV file, the ContentID column could be left "blank", which would result in Pega Knowledge creating new content ID's during the import. The ContentType column should specify "URL", and then each ContentBody cell would contain the Sharepoint URL's for each article (each article representing a row in the .CSV file.
2) A second approach involved more of an integration effort, where either the existing Sharepoint index of the repository is made available to Pega's Elastic search engine, so when an article search or suggestion is being made, Elastic would parse both indexes (Pega Knowledge index and the Sharepoint index) and "collate" the results, determining the most relevant results from both indexes to return to the search or suggested content function in the UI. Note that Pega does not provide a spidering/crawler capability, so that may be required if the solution requires crawling and indexing the Sharepoint repository.