Property | Description | |
Model type | Specifies the content model for this document type. The content model provides a formal description of the structure and allowed content for a document type which can then be used to validate an instance document. The Model type property is display-only. To change the model type for a document type, modify the XML schema definition, and recreate the document type. The contents of an IS document type with a Model type property value other than “Unordered” cannot be modified. The Model type property can have one of the following values: | |
Value... | Description... | |
All | All of the fields in the document type must appear once or not at all, and in any order, in the instance document. The all model type corresponds to an complex type definition that contains an all compositor in the model group. | |
Choice | One and only one of the fields in the document type can appear in the instance document. The choice model type corresponds to an complex type definition that contains a choice compositor in the model group. | |
Sequence | Fields in the instance document must appear in the same order in which they are declared in the document type. The sequence model type corresponds to an complex type definition that contains a sequence compositor in the model group. | |
Simple | A single field that contains simple content and carries an attribute. The document type contains an @attributeName field for the attribute value and a *body field for the simple content. | |
Unordered | Fields in the instance document can appear in any order and any number of times. A document type has a model type of Unordered if any of the following are true:  The document type was created using Developer.The document type was created using a version of Integration Server prior to version 8.2.The document type was built manually or created from a source file besides an XML schema definition.If the document type was created from an XML schema definition, the Compliance option was not set to “strict” at the time the document type was created.If the document type was created from an XML schema definition that contained repeated or nesting model groups, the any element, or the any attribute and the Compliance option was set to “lax” at the time the document type was created.Note: An unordered data structure is sometimes referred to as a “bag” data structure. | |
Permissions | Click  to assign or view ACL permissions to a document type. | |
Reuse | Specifies whether this element can be dragged from the CentraSite Registry Explorer view to a BPM process or CAF project. When this property is set to public, you can drag the asset to a BPM process or CAF project. When this property is set to private (the default), you cannot drag the asset to a BPM process or CAF project. All published assets are available for Impact Analysis, whether they are public or private. Although changing the public/private status will immediately change whether or not you can drag an element to a BPM process or CAF project, the element's status in CentraSite will not change until the next publication of assets to CentraSite. | |
Source URI | Displays the location or URI of the source used to create this document type. If this document type was not based on a source and was instead created from scratch, the Source URI property is empty. | |
Linked to source | Indicates whether the document type reflects the content and structure of the source from which it was created. When set to true, the contents of the document type cannot be edited. When set to false, the document type can be edited but may no longer accurately reflect the content and structure of the source. | |
Schema domain | Displays the name of the schema domain to which IS schemas generated for this document type belong. This property applies to IS document types created from XML Schema definitions only. Note: When Integration Server consumes a WSDL document to create a web service descriptor, Integration Server places any generated IS schemas in a unique schema domain for that web service descriptor. Integration Server uses a combination of alphanumeric characters as the schema domain name. | |
Registered | Indicates whether Integration Server registered an association between the document type and the complex type definition from which it was created. This is used for derived type support. This property applies to IS document types created from XML Schema definitions only. | |
Schema type name | Displays the name of the complex type definition with which the IS document type is registered. This is the complex type definition from which the IS document type was created. This property applies to IS document types created from XML Schema definitions only. | |
Sync to DES | Indicates whether Integration Server automatically synchronizes this document type with a corresponding Digital Event Services event type definition in the Digital Event Services repository upon save. When set to True, Integration Server automatically synchronizes the document type. Upon the first save of the document since setting Sync to DES to True, Integration Server creates a Digital Event Services event type definition that corresponds to this document type. In addition to synchronizing this IS document type, Integration Server also synchronizes any IS document type that is referenced by this IS document type. The default value for Sync to DES is False. A document type does not need to be a publishable document type for Sync To DESto be set to True. Instances of a document type for which Sync to DES is set to True might not be published to Digital Event Services Instead, the document type is used to define the structure and content for the value of an "any" field in a document that is published to Digital Event Services. An instance of document type used to define an Any field at publication time must have an updated, corresponding Digital Event Services event type definition. By configuring Integration Server to synchronize the document type to Digital Event Services repository automatically upon save, you ensure that an updated, corresponding Digital Event Services event type definition exists. For Integration Server to synchronize a document type to Digital Event Services automatically upon save, the IS_DES_CONNECTION alias must be enabled. | |