The task model is a description of each task in a workflow. It defines attributes associated with that task. A user interface component can use this description to automatically generate an interface suitable for displaying the task information, in addition to initializing a newly created task instance.
The client configuration allows for customization of the UI component that is used for presenting workflow‐related information to the user and taking inputs from the user. Content Services uses resource bundles to select the text that displays. Resource bundles allow language-specific strings to be used to display information about a workflow or task. The following diagram shows the relationship between the process definition and the task model on the server, and the client configurations and resource bundle in the client.
When creating workflows you’ll need to create the process definition using the graphical designer, create a task model to define your specific metadata items required on a task, and optionally look at customizing the user interface to support the custom task model that you’ve defined. Using a resource bundle is optional.
Content Services ships with two default workflow models that support the default set of process definitions.
| Workflow Model | Description |
|---|---|
| bpmModel.xml | Is the basic workflow content model |
| workflowModel.xml | Contains more detailed task types and specializes the basic task types from the BPM model |
The following diagram shows the models in detail.
The task model is important when considering user interfaces, as the properties from task types are the only properties which can be shown to the user.