Skip to content

Content Types

Use content types when the same form structure should be reused across multiple processes, or when a case or document needs a reusable profile form.

Unlike form templates, which stay inside one process definition, content types are independent entities. They are published separately and updated from their source definition. The content type's data model is packaged with the form and imported into the using process.

Creating Content Types

To create a content type:

  1. Create a form template.
  2. Link the form template to a content type.

Using Content Types in Forms (Dynamic Forms)

The ContentType widget renders a content type dynamically within a form:

1
2
3
<ContentType TypeXPath="Type" TargetXPath="Content">
    <Rules/>
</ContentType>

TypeXPath: XPath to the field containing the content type name. TargetXPath: XPath specifying the container element where the template's data model will be imported.

Content Type Data Source

The content type name can be set manually or dynamically using a ContentTypeDataSource with a list control:

1
2
3
4
5
6
7
<DropDown XPath="Type">
    <DataSources>
        <ContentTypeDataSource Enabled="True">
            <Mappings/>
        </ContentTypeDataSource>
    </DataSources>
</DropDown>

Content Types as Profile Forms

Content types serve as profile forms for both documents and cases:

  • Document Profiles: When creating a document, available content types are listed, allowing users to select a profile form.
  • Case Profiles: Similarly, content types are available for selection when creating new cases.