11-28-2014 04:37 AM
custom:type
we want to set a custom mimetype as default mimetype (lets say application/custommimetype
if a document is created as custom:type
. For this I tried to override the parent type's property <default>application/custommimetype</default>
mimetype for both cmis:contentStreamMimetype
(in case our parent type is cmis:document
) and cm:content.mimetype
(in case our parent type is cm:content
.
<imports>
<!– Import Alfresco Dictionary Model Definition –>
<import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d" />
<!– Import Alfresco Content Domain Model Definition –>
<import uri="http://www.alfresco.org/model/content/1.0" prefix="cm" />
<!– Import Alfresco Repository System Model Definition –>
<import uri="http://www.alfresco.org/model/system/1.0" prefix="sys" />
<!– Import Alfresco Share Data List Model Definition –>
<import uri="http://www.alfresco.org/model/datalist/1.0" prefix="dl" />
<!– Import Alfresco CMIS Model Definition –>
<import uri="http://www.alfresco.org/model/cmis/1.0/cs01" prefix="cmis" />
</imports>
[…]
<type name="custom:type">
<title>Custom Type</title>
<parent>cm:content</parent> //or <parent>cmis:document</parent>
<properties>
<property name="custom:property">
<title>Custom Property</title>
<type>d:text</type>
<mandatory>true</mandatory>
<multiple>false</multiple>
</property>
</properties>
<overrides>
<property name="cm:content.mimetype"> //or <property name="cmis:contentStreamMimeType">
<mandatory>true</mandatory>
<default>application/custommimetype</default>
</property>
</overrides>
</type>
12-01-2014 10:32 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.