createAssociation operation (deprecated)

Creates an association between two contents in the repository.

For information about the General and Route Evaluation property groups, see Common operation properties.

Input properties

Properties to specify the contents and the type of relationship between them.

Store Name

A string value that represents the name of the store where the content is located.

If you provide a literal value, select the name from the list. Currently, only SpacesStore is available.

Association Type

A string value that represents the type of association between the two contents.

If you provide a literal value, select one of the following options:

attachedTo:
An association between an attachment and the data XML file. The attachment must have the aspect attachable applied to it. It is a many-to-one association, which means that multiple attachments can be associated with an XML file.

linkedBy:
An association between an XML data file and a PDF form. The XML file must have the aspect linkable applied to it. It is a many-to-one association, which means that multiple data files can be associated with the same PDF form.

linkedTo:
An association between two PDF documents. The source document must have the aspect PDFToPDFLink applied to it. It is a many-to-one association, which means that two or more documents can be linked together.

linkedToXML:
An association between an XDP Document attachment and the XDP data XML file. The attachment must have the aspect xdpAttachment applied to it. It is a many-to-one association, which means that multiple XDP Document attachments can be associated with a single XML file.
Hinweis: After selecting an association type, when you click inside any other box in the Input panel, a text below the Association Type field shows the mandatory aspect related to the selected association type. For example, for the attachedTo aspect type, the following line is displayed below the field:
Parent Aspect = attachable

Parent Node ID/Path

A string value that represents a fully qualified name or a unique identifier of the parent node. The path must start from the root location (for example, /Company Home/User Home/My Home/Mydata.xml).

If you provide a literal value, either type the path or identifier or click Browse to select the content node.

Child Node ID/Path

A string value that represents a fully qualified name or a unique identifier of the child node. The path must start from the root location (for example, /Company Home/User Home/My Home/Mydata.xml).

If you provide a literal value, either type the path or identifier or click Browse to select the content node.