Skip to main content

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

Technical details for the manage requirement documents screen

Updated on January 18, 2022

The Manage Documents screen is displayed using the ManageReqDocLinks section and its referencing flow action.

The Upload and Link screen is displayed using the AttachFileBrowseMultiOptionCMIS section and its referencing flow action.

The uploading and linking of the document is handled by the UploadAndLinkDocument activity.

The document upload is handled by Step 7 of the activity.

As described earlier, the document upload includes metadata. This is configured in the pySaveFileContent activity. Step 11 of the activity has been configured to add the required metadata, which is uploaded as properties associated with the document. Note that the property IDs or names in this example are specific to an Alfresco server. If you use a different CMIS server, then modify the property names per the configuration of the CMIS server.

The basic CMIS upload functionality has been extended for uploading a new version of the document using the InvokeCMISConnector activity. Step 11 has been updated for the change; this works for any CMIS server. No specific updates are needed at this level for uploading a new version of the document.

All operations related to the CMIS use this activity. Be careful when modifying any of the functionality in the specified activity.

As shown earlier, the Matching Document section in the Manage Documents screen employs search on the CMIS server, based on the uploaded metadata. That is, it uses the uploaded document metadata to search for the document. This is done in the FindECMDocuments activity. Step 8 calls the PrepareCMISQuery data transform that sets the necessary details for searching. Additional metadata configured could be added to the query if you want to use that metadata to search for the data transform.

Once the document has been uploaded, a provision automatically uses the LinkSelectedDocument activity to link the uploaded document to the selected Document Requirement. That activity, in turn, calls the LinkSelectedDocumentToCase data transform, which sets the necessary properties required for linking the document to the requirement. The document commentary is also updated as a part of this data transform. The same activity is also used when you click on the Link button, thus maintaining a consistent process.

As described earlier, a linked document includes an Unlink button. Click it to unlink the document from the Document Requirement. This is done using the unlinkDocument activity.

  • Previous topic Configuration to support customer properties metadata
  • Next topic Configuring Pega Platform to act as a CMIS server

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