Creating a compound document

Hi,

Does anyone know how to create a compound document? Also, if I create a compound document, is this essentially a Node that becomes the parentID for the docs that I want to insert into it?

Thanks,

Matt.

Find more posts tagged with

Comments

sgrasley

Hi, Matt.

Yes, you can create a node of type "CompoundDoc" and then create documents inside of it (i.e. using the compound doc's ID as the parent ID).

The DocumentManagement service also has methods specific to compound docs, like CreateRelease, RepositionNode, etc.

Thanks,

Scott

Matt Eustace

Thanks Scott!

I am having an issue with my createNode call though - specifically with the metadata section. The service is responding with "Unknown AttributeGroup types {?}." where I am setting up the metadata. I think the problem is with the Description tag in the following:

<urn1:Values>
                     <urn2:Description>Matt</urn2:Description>
                     <urn2:Key>15643.3.2</urn2:Key>
                  </urn1:Values>

Where I expect this to be the value to insert. I've tried a few different things like urn2:Value instead of description, but can't figure out what I am doing wrong. Complete call is shown below.

Thanks, Matt.
-------

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:DocMan.service.livelink.opentext.com" xmlns:urn2="urn:Core.service.livelink.opentext.com">
   <soapenv:Header>
      <urn:OTAuthentication>
         
         <urn:AuthenticationToken>bDWhHQygy%2B3fYI%2FRz455ti35ncVwLt8C6Iu7hDyd2rRfw70DeZUPn186VH6Dy3HK</urn:AuthenticationToken>
      </urn:OTAuthentication>
   </soapenv:Header>
   <soapenv:Body>
      <urn1:CreateNode>
         
         <urn1:node>
            <urn1:Catalog>0</urn1:Catalog>
            <urn1:DisplayType>Coumpound Document</urn1:DisplayType>
            <urn1:IsContainer>true</urn1:IsContainer>
            <urn1:IsReference>false</urn1:IsReference>
            <urn1:IsReservable>true</urn1:IsReservable>
            <urn1:IsVersionable>false</urn1:IsVersionable>
            
            <urn1:Metadata>
               
               <urn1:AttributeGroups>
                  
                  <urn1:DisplayName>HR Global</urn1:DisplayName>
                  
                  <urn1:Key>15643.3</urn1:Key>
                  
                  <urn1:Values>
                     <urn2:Description>Matt</urn2:Description>
                     <urn2:Key>15643.3.2</urn2:Key>
                  </urn1:Values>
               </urn1:AttributeGroups>
            </urn1:Metadata>
            <urn1:Name>ws created cpd</urn1:Name>
            <urn1:ParentID>15091</urn1:ParentID>
            
            <urn1:Permissions>
               <urn1:AddItemsPermission>true</urn1:AddItemsPermission>
               <urn1:DeletePermission>true</urn1:DeletePermission>
               <urn1:DeleteVersionsPermission>true</urn1:DeleteVersionsPermission>
               <urn1:EditAttributesPermission>true</urn1:EditAttributesPermission>
               <urn1:EditPermissionsPermission>true</urn1:EditPermissionsPermission>
               <urn1:ModifyPermission>true</urn1:ModifyPermission>
               <urn1:ReservePermission>true</urn1:ReservePermission>
               <urn1:SeeContentsPermission>true</urn1:SeeContentsPermission>
               <urn1:SeePermission>true</urn1:SeePermission>
            </urn1:Permissions>
            <urn1:Type>CompoundDoc</urn1:Type>
            
            <urn1:VolumeID>-2000</urn1:VolumeID>
         </urn1:node>
      </urn1:CreateNode>
   </soapenv:Body>
</soapenv:Envelope>

sgrasley

Hi, Matt.

If you call GetCategoryTemplate for the category that you want to use, it will build the elements for you. Then you can pass them into your CreateNode call. In this case, there is a Type element that needs to be provided to indicate that it's a category you want to use.

Thanks,

Scott