There are two main types of fields that are used in the workflow system: workflow fields and database fields.
Workflow fields | Workflow fields are all of the user fields and system fields that are associated with a single workflow. A workflow field is a workflow property, which means that it can be used in one or more steps of a workflow. When the workflow is running, a field value set at one step will be available in subsequent steps that use the same field. The value of each field in a workflow is limited to the current instance of the workflow; each time the workflow runs, the values in the fields can be different, and can change as the workflow processes. There are two types of workflow fields:
|
---|---|
Database fields | You can create database fields to store the values of corresponding source fields (such
as workflow fields) so that these values become searchable. In particular, database fields
can be used for the following purposes:
A database field is part of a workflow structure such as a roster, queue, or event log. The database field and the source field must have the same name and the same (or similar) data type. Integer and float data types can be mixed. Database fields are also known as exposed fields. Adding a field to the list of exposed fields does not create the field—the workflow author does that. In the same way, removing a field from the list of exposed fields does not delete the field—it simply makes the field unavailable for the uses listed above. Important: The creation of database fields can adversely affect system
performance in the following ways:
|