Update metadata via CMIS in Document Management System
I am working on a POC to upload and update files from Pega to Alfresco Documentum managment system.
Followed instructions from PDN (https://community.pega.com/) and configured CMIS connector.
I am able to test connectivity through Connect CMIS rule to Documentum also able to browse for the CMIS folder able to attach docs from case.
But I could not find any topics how to update metadata via CMIS from Pega. It seems the 7.3 support only these features: https://community.pega.com/marketplace/components/content-management-interoperability-services-cmis
Is there any way to update metadata from pega?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
Pega's CMIS Connector API supports the "update properties" method of CMIS.
These are the CMIS properties you're talking about:
- cmis:name
- cmis:description
You should be able to create an Activity rule for accomplishing this task (and call it however you see fit):
- Create a CMIS-UpdateProperties page
- Add a row to the page's ".pyProperties.pyPropertyString" list
- set pyPropertyDefinitionId to the identifier (such as "cmis:name")
- add a row to the pyValue list of this row in pyPropertyString containing the new name
- (Run CMIS connector with this request page)
Accepted Solution
Pegasystems Inc.
US
Pega's CMIS Connector API supports the "update properties" method of CMIS.
These are the CMIS properties you're talking about:
- cmis:name
- cmis:description
You should be able to create an Activity rule for accomplishing this task (and call it however you see fit):
- Create a CMIS-UpdateProperties page
- Add a row to the page's ".pyProperties.pyPropertyString" list
- set pyPropertyDefinitionId to the identifier (such as "cmis:name")
- add a row to the pyValue list of this row in pyPropertyString containing the new name
- (Run CMIS connector with this request page)
Pegasystems Inc.
US
Was "Pega7.23" a typo? What version are you mentioning here?
This is out-of-the-box functionality.
Please create a new post if you are having trouble getting it to work, as the question on this post has already been answered.
Accenture
US
just revisiting the old thread; is there any option to save the content to a custom type vs. the OTB type within the repository. For e.g. the base type is dm_document and I create a type ent_custom_type with 3 attributes which is inherited from dm_document, can Pega be configured to write against the ent_custom_type and update the 3 attributes? any assistance/guidance would be greatly appreciated
Pegasystems Inc.
US
Mahesh, your question has a very loose relation to the original post. Please post your question separately in order to avoid muddying this discussion thread.