SBM Composer Reference → Application Field Reference → Field Reference → System Fields for Primary Tables → Optional System Fields for All Primary Tables
Optional system fields for primary tables lets you collect additional data to enhance your tracking system. Create these fields when setting up the primary table for your application in SBM Composer.
The following table describes the optional system fields that are available for primary tables.
Field Name | Notes |
---|---|
Close Date | An auto-populated Date/Time field that records the date and time items are transitioned to an inactive state. If the item is later moved to an active state, the Close Date value is cleared. If you do not add the Close Date field to your application, the close date and time are still captured in various areas, such as the state change history and the timestamp for Text/Journal fields. Adding the Close Date field to your system lets users query for this information in search features and reports, particularly State Change reports. |
Description | By default, the system Description field is a Text Memo field that is set to allow keyword searching. |
Last Modifier | An auto-populated
User field that records which user last changed an item.
The value of the
Last Modifier field changes as items are updated and
transitioned through a workflow. All users who can update and transition items
into the system are available as values for this field, but you can control who
updates and transitions items through privileges.
If you do not add the Last Modifier field to your primary table, the name of the user who last modified an item is still recorded in the change history. Adding the Last Modifier field to your primary table lets users query for this information in search features and reports. |
Last State Change Date | An auto-populated Date/Time field that records the date and time an item last moved to another state. The value of the Last State Change Date field changes as items are transitioned to different states. The Last State Change Date field is useful for searching and reporting on items based on the last date and time they were last moved. To view a complete history of state changes for particular items, users can create State change reports. |
Last State Changer | An auto-populated
User field that records the user who last moved an item to
a new state. The value of the
Last State Changer field changes as items are transitioned
through a workflow. All users who can transition items into the system are
available as values for this field, but you can control who transitions items
through privileges and transition restrictions.
If you do not add the Last State Changer field to your application, the Change History section shows who moved items from state to state. Adding the Last State Changer field to your application lets users query for this information in search features and reports. |
Pause Status | An auto-populated Pause Status field that shows why an item is paused by Demand Manager. A paused item cannot use transitions that move it to another state. |
Submitting Agent | An auto-populated User field that records the user who submits an item on behalf of another user. |
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.