Migrating Legacy KM to Pega KM Platform ( PRPC 8.1)
Hi All ,
We are in PRPC 8.1 . We are planning to migrate our legacy KM articles into Pega KM . We plan to use the import wizard provided by Pega KM but we are having some challenges around images referenced within the legacy KM articles . Below are the questions . Appreciate if someone can provide guidance
1) Legacy KM has a lot of images and we need to move these images within Pega KM and change the image reference within the articles before we use the import wizard . What is the best way to do it . How do we upload the images within Pega . We would get the zip file of the images . Should we place it in App Server or load each of it as Image Content instances?
2) We do not see "Browse Server" button when we try to insert image into KM article within the rich text editor . The "Browse Server " button is available for paragraph rule . Was it intentional not to show it in KM as the images are uploaded as Image Content instances . How would the user be able to see existing images ?
3) When we upload a image using the rich text editor , we see an instance is created for the Image content but the file name is appended with a random number . What is the reason behind this .
Thanks
Dinesh
Accepted Solution
Pegasystems Inc.
IN
The image should be in a folder that can be accessed using its absolute URL. Use the same absolute URL in RTE when editing an image.
Pegasystems Inc.
IN
We would recommend to upload these images to some repository and use urls in the articles as a reference to the image. KM uses RTE and not Paragraph rule, hence you do not see the browser server icon .
JP Morgan Chase
IN
Thanks Sawant ,
Thanks for the response . Just want to have some more clarity here . We are on pega cloud . When you mention some repository ,is it the app server ? If not , what other options do we have . Also if we plan to have images in a repository how should the image management happen when we are creating a new KM article . If we use the RTE those get created as Image Content instances . With this we would end up having images in 2 different places .
Thanks
Dinesh
Pegasystems Inc.
IN
The repository can be app server if cloud team can upload them else another server should serve as image repository. This will serve the image links in existing articles.
RTE does not support browsing images on server. Only local files can be uploaded first. Although, it allows to provide a image URL when uploaded image is edited. So to add a image from repository this work around can be used. We will check with platform if we can get the feature to specify an image URL.
JP Morgan Chase
IN
Thanks Sandeep for the additional details . We will reach out to cloud team to see if we can get it on app server . For the work around can you provide how to specificy URL , would it be like for exm \temp\image1.jpg .
Also i am thinking from the business team , they would be adding articles / modifying content and they would need IT help to have new images added to the repository which i believe wont work . We would want to have one consistent solution for maintenance of images .
Thanks
Dinesh
JP Morgan Chase
IN
Hi Sandeep ,
The work around doesnt seem to work . Can you please provide an example of how to refer an image from the app server . Pega OOTB is always looking at temp/staticcontent/datacontent folder . Even if i put the image in this location and try to access , it still doesnt work .
Thanks
Dinesh
Accepted Solution
Pegasystems Inc.
IN
The image should be in a folder that can be accessed using its absolute URL. Use the same absolute URL in RTE when editing an image.