Administrative Area Components

• User
• Group
• Containered Asset
• Asset Factory
• Asset Factory Container
• Page Configuration Set
• Page Configuration Set Container
• Structured Data Definition
• Asset Factory Container
• Metadata Set
• Metadata Set Container
• Publish Set
• Publish Set Container
• Target
• Destination
• File System Transport
• FTP Transport
• Workflow Definition
• Workflow Definition Container

NEWS & TIPS

• Site Access Keys
• Top: Alt+t
  Previous: Alt+,
  Next: Alt+.
  Up: Alt+;
  (Note: use Ctrl on the Mac)

Asset Factory

An Asset Factory is defined in the following WSDL:

<complexType name="assetFactory"> <complexContent> <extension base="impl:containered-asset"> <sequence> <!-- comma-delimited list of strings for which this asset factory is available NOT REQUIRED default: empty --> <element maxOccurs="1" name="applicableGroups" type="xsd:string"/> <!-- The type of asset this factory will create REQUIRED --> <element maxOccurs="1" minOccurs="1" name="assetType" type="xsd:string"/> <!-- The default/base asset for this factory: assets created using this factory are initially populated with this asset's data. NOT REQUIRED default: none --> <choice> <element maxOccurs="1" minOccurs="0" name="baseAssetId" type="xsd:string"/> <element maxOccurs="1" minOccurs="0" name="baseAssetPath" type="xsd:string"/> </choice> <!-- where assets created from this factory must be placed if specified NOT REQUIRED default: none --> <choice> <element maxOccurs="1" minOccurs="0" name="placementFolderId" type="xsd:string"/> <element maxOccurs="1" minOccurs="0" name="placementFolderPath" type="xsd:string"/> </choice> <!-- when the placement folder is specified, this allows assets to be placed in subfolders of that folder as well NOT REQUIRED default: false --> <element maxOccurs="1" minOccurs="0" name="allowSubfolderPlacement" type="xsd:boolean"/> <!-- assets created from this factory will be positioned at this folder position NOT REQURIED default: 0 --> <element maxOccurs="1" minOccurs="0" name="folderPlacementPosition" type="xsd:nonNegativeInteger"/> <!-- If an asset is created from this factory and placed in a folder with an asset of the same name, whether or not that asset will be overwritten. NOT REQUIRED default: false --> <element maxOccurs="1" minOccurs="0" name="overwrite" type="xsd:boolean"/> <!-- What workflow behavior to use when creating assets using this asset factory REQUIRED --> <element maxOccurs="1" minOccurs="1" name="workflowMode" type="impl:asset-factory-workflow-mode"/> <!-- When workflowMode is "factory-controlled", this specifies the workflow definition to use NOT REQUIRED default: empty --> <choice> <element maxOccurs="1" minOccurs="0" name="workflowDefinitionId" type="xsd:string"/> <element maxOccurs="1" minOccurs="0" name="workflowDefinitionPath" type="xsd:string"/> </choice> </sequence> </extension> </complexContent> </complexType>

An Asset Factory extends Containered Asset. In addition to the fields provided by that complex type, the asset factory complex type implements all the fields as available from within the Cascade Server web interface when creating or editing. The required fields are as follows: created asset type and workflow mode.

Things to be aware of: the workflow mode is defined by the following simple type restriction:

<simpleType name="asset-factory-workflow-mode"> <restriction base="xsd:string"> <enumeration value="folder-controlled"/> <enumeration value="factory-controlled"/> <enumeration value="none"/> </restriction> </simpleType>

This says that the workflowMode element must be populated by a String of the form "folder-controlled", "factory-controlled", or "none". If "factory-controlled" is specified, then the workflowDefinition relationship must be specified using the ID or path of a Workflow Definition.

Comments

Wiki | Edit