Applications → Managing Fields → About Fields → System Fields → System Fields for Primary Tables → Required System Fields for All Primary Tables
Required system fields for primary tables gather necessary data for your tracking system and help ensure that the process you define is followed. Required system fields are automatically added to all primary tables. These fields cannot be deleted or moved into the Not Used section. You can, however, move them into the Hidden field section. You can edit these fields and change certain property settings and move them to different field sections.
The following table describes the system fields required for primary tables. The field icon is provided, along with information and special considerations for each system field.
|Active/Inactive||A Binary/Trinary field that indicates a primary item's status. States use the Active/Inactive field to automatically determine the status of items in each state. In SBM Composer, you can change the active and inactive labels. The Active/Inactive field is always shown on forms as a drop-down list.|
An auto-populated Text field that numbers primary items based on project settings defined in SBM Application Administrator.The Item ID is used to identify and locate items in the ID Search feature, SourceBridge, reports, and more. If your Item Type field uses prefixes, they are prefixed to the Item ID.
A Single Selection field populated with the types of items you wish to track, such as defects and enhancement requests. Specify a three-letter prefix that is prefixed to the Item ID. For example, a defect might have an Item ID of DEF00011 and an enhancement might have an Item ID of ENH00025.
You can tailor your process to manage each item type differently, if needed. For example, you can modify a workflow by restricting the item types available for certain transitions.Note By default, the Item Type field is not set as required. For best results, set the field to be required as items are added to the system.
|Last Modified Date||An auto-populated Date/Time field that indicates the date and time an item was last updated. This information is used for auditing and establishing change history for items.|
|Owner||An auto-populated User field indicating the current primary owner of an item. The value of the owner field is determined by the state in which an item resides and changes as items are transitioned through a workflow. In SBM Composer, you select a User field type as the value for the Owner field for each state in the General tab of the state Property Editor.|
|Project|| A system
Project field populated with all projects in an
application. If users change the value of the
Project field for a specific item, they are also moving
that item to the specified project. Depending on your workflow and project
relationships, the item could follow a different process than you intended. To
avoid this problem, set the field to read-only or move it to the Hidden
Note: Projects are defined in SBM Application Administrator.
|State||A system State field populated with all states for a specific workflow. If users change the value of the State field for a specific item, they are also moving that item to the specified state in the workflow and it could follow a different process than you intended. To avoid this problem, set the field to read-only or move it to the Hidden field section or restrict the section according to privileges.|
|Submitter||An auto-populated User field indicating the user who submitted an item. Users whose privileges include submitting items into the system are available as values for this field.|
|Title||An 80-character fixed-length Text field. The system Title field is displayed by default in many areas, such as built-in report and search results. This is the optimal display length for displaying item titles to users. You can increase the character length of the system Title field. However, doing so could return unexpected results.|
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.