Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring Pega Platform to act as a CMIS server

Updated on January 18, 2022

As discussed, the Manage Documents functionality leverages multiple features of Content.

Management Interoperability Services (CMIS) standards, which requires a CMIS server. But what if a CMIS server is not configured?

In that case, you can configure Pega Platform to act as a CMIS server. This requires that you create a Connect-CMIS rule with “PRPC” as the Atom Server. By default, Pega Platform does not include the capabilities that are provided by a CMIS server; therefore, you must create a dummy Connect-CMIS rule in the application named “PRPC”.

While uploading a document with another CMIS server in place, Pega Platform usually maintains a pointer to the CMIS object. If the CMIS server is Pega Platform, the page updates with metadata details that the CMIS-related activities have built, and the object is saved to the database table mapped to the Data-WorkAttach-File class. The way that the metadata is built has not changed.

However, the metadata page is now stored in the BLOB column of the Pega Platform table.

The ManageContentThroughPRPC activity (see the following screen) shows the changes that were made for uploading the attachment object to Pega Platform with the metadata built for CMIS. This activity is called in the InvokeCMISConnector activity. The flow branches out to this activity when the connector is Pega Platform; otherwise, it continues its normal protocol of connecting to the CMIS server.

The only other change for uploading a version document in Pega Platform is done in the pySaveFileContent activity. Step 14 has been added to update the version manually since Pega Platform does not have a mechanism to increment the version when uploading a document.

The metadata update is carried out in the pySaveFileContent activity according to the Requirement. All the updates are persisted in the database. During the retrieval of the metadata, it is mapped to specific properties as required by CMIS for proper display. The ManageContentThroughPRPC activity maps the metadata retrieval as shown in the following steps:

After the document has been uploaded, the latest uploaded object’s details are displayed and then mapped to the required properties for display in the UI (as shown in the screenshot above). For anyone extending the functionality, you need to update this step.

Search for the label provided during the metadata upload, and then set the value to the required property. Note that search uses the same functionality.

The DownloadContentStream activity is updated to add the steps needed for downloading and opening a Pega Platform document.

In addition, a new SetCMISSearchParams data transform is added to set the required metadata on a temporary page for use by the upload, link, and search functionalities of CMIS. If you extend the functionality, update this data transform to set the required metadata on this page and use it later. This is called by the SelectAttachment activity, which is called when you click Manage Documents on the Requirements page.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us