The Individual Template Tables
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Each template registered on the server is stored in an individual template table. Each row in this table holds information about a template component, such as the template database, forms, and views. The table contains complete information about the template. No part of the template is stored outside the table and referenced from within the table. As a result, a template can be persisted as a file from the Workflow Manager for SQL Server. Then, the file can be sent to other servers that have the Workflow Services for SQL Server installed, imported into the Workflow Manager, and stored as a template on the new server.
The advantage of having one table for each template is that you can store independently many elements of the same type, such as forms or component files, and can access them directly. Because each component represents a row in the table, the components can be located and loaded from the template at run time.
The server on which a template is deployed must have the same configuration as the server on which the template has been built.
**Note **You should not alter the template tables manually. Use the Workflow Designer for SQL Server and the Workflow Manager to make changes. Schema integrity is not guaranteed if you make manual changes to any system tables.
The following table lists the individual template table columns and their data types and provides a brief description of each.
| Column | Data type | Description |
|---|---|---|
| Id | identity (int) | Unique identifier for each template component. |
| Name | nvarchar(128) | Name of the template component. |
| Caption | nvarchar(255) | Friendly name of the template component, displayed with the component (for example, "Main Issue Tracking Form"). |
| Description | ntext | Text describing the template. This information is entered when using the SQL Server Workflow Template Creation wizard. |
| Type | char(2) | Object type:
|
| Value | image | A binary field that holds the value of each component (for example, the database snapshot, a data access page file, or a component file). |
| Properties | text | Reserved for user-defined properties. |
See Also
ModSystem Database Tables | The modApplications Table | The modTemplates Table | The modUserList Table | The modProperties Table (modSystem Database)