Applications → Managing Fields → About Fields → Field Types
Two categories of fields are provided:
All primary and auxiliary tables contain system fields that help gather data needed by the tracking system. Some system fields are required, but others are optional. For a list of system fields for each table type, refer to Application Field Reference.
SBM provides a diverse set of field types that you can add to the primary and auxiliary tables in your applications.
The following sections describe the type of custom fields available to you.
The following fields represent simple values stored within database tables. These field types are the most efficient and provide the best performance when used in reports.
| Can store either two values or three
values of your choosing.
Use two values for situations where you need to give users "yes/no" or "on/off" options.
Use three values when you need an additional option, such as a value that helps determine subtask status.
| Store dates and time values.
Date/Time fields can be displayed as the date only, date
and time, time only, or elapsed time.
Date/Time values are shown to users in the format provided in their user profile.
| Store integers, floating point values, or
fixed precision values.
Numeric fields can be used as weights in Trend reports.
|Sums the values of weights of Single Selection fields or values for Numeric fields set as integers.
Can be of fixed length up to 255 Unicode characters, Memo type (whose length varies by DBMS), or a Journal type.
SBM supports non-ASCII characters in Text field values, allowing runtime data to be displayed in a wide variety of international languages.
You can enable Rich Text editing for Memo and Journal fields.
The following field types represent users or groups in your systems. Values for these field types can come from roles defined in SBM Composer and from users and groups defined in SBM Application Administrator. For details, refer to Values for User, Multi-User, and Multi-Group Fields.
User field types are also used to establish ownership for primary items. For details, refer to Ownership of Items.
|Enables users select one or more groups to associate with an item.
|Enables users to select users, groups, or group members as values for the fields. The type of selections available depend on settings you apply for the field in SBM Composer.
| Enables users to select a single user or
group member to associate with an item.
System User fields, such as Owner and Submitter, are indicated by a red circle in the bottom left corner of the User field icon.
The following field types enable users to select values you define for the field in SBM Composer. Use this field type for static values that will likely not change over time. For example, use a Single Selection field to create a Priority field that may have values of High, Medium, or Low.
If values will change on a regular basis, consider using Single Relational or Multi-Relational fields instead.
|Enables users to select one or more predefined values.
| Enables users to select one predefined
You can assign weights to each value to assist with reporting, backlog views, and Summation field values.
Single-Relational and Multi-Relational fields are used to establish relationships between data in primary and auxiliary tables. These field types are ideal for managing values that will change over time.
For example, you may have a Products auxiliary table that stores information about the products your company sells. Each product has its own record in the Products table. You can create a Multi-Relational field in your process app that points to the Products table, enabling users to select the products that relate to a particular work item. As your company adds products, you can easily add records to the Products table.
Relational fields are created in SBM Composer, but Relational field values are typically added using the Auxiliary Data feature in SBM Application Administrator.
The following information applies to Relational fields:
|Enables users to select one or more items from a primary or auxiliary table as values for the field.
|Enables users to select one value to associate with a particular primary or auxiliary table.
|Allows access to additional fields in a related primary or auxiliary table. Sub-Relational fields are tied to a Single-Relational field already in an application. For example, if an Incidents table contains a Single-Relational field to an Issues table, you can include a Sub-Relational field of Owner. This lets users see the owner of a related issue within the incident. Sub-Relational fields are only available if Single Relational fields already exist for a particular table.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.