Field Properties within Layouts

Not every field can be added successfully to every layout, and there are limitations regarding the placement of many fields on repeating record layouts. The following table gives an indication of all inbuilt fields and their restrictions in use. Note that User Defined Fields are capable of being placed on all layouts, subject to the field belonging to the correct type of issue records or repeating row records for the layout, and as long as the data dictionary entry for the field is defined correctly. Note that there are limitations with layout cell attributes between fields of different types. You may not have a layout cell attribute where a field of type issue record is dependent upon a field of type repeating row. The renderer, in this case, would not know which repeating row to use for its logic check.

Data dictionary field name- DATABASE field types Notes
ALT_ID Any layout except repeating record layouts
AREA All Add and Edit layouts belong to a specific Business Area. If the AREA field is placed on the layout, then the field and its values will be presented in the normal way. If the AREA field is not placed on the layout, then ExtraView processes the layout as if the value of the Business Area is set to the same value to which the layout belongs. This helps the usability for many applications where there is more than one Business Area, but you want to restrict the user to only working within a single Business Area at a point in time, for example, when you have a popup window to enter a child issue which will be placed within a specific Business Area. If you want to restrict the user to only being able to address a subset of the available Business Areas within an installation, you may use the FIELD HIDE VALUES and the FIELD VISIBLE VALUES to restrict the displayed values.
ASSIGNED_TO Any layout except repeating record layouts
ATTACHMENT_ID Internal use only
ATTACH_CONTENT_TYPE Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_CREATED_BY_USER Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_DATE_CREATED Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_FILE_DESC Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_FILE_NAME Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_FILE_SIZE Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_PATH Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
ATTACH_THUMBNAIL Will be placed automatically on the layout as part of the attachment record. Controlled by security permissions
AVAILABLE_FOR_DOWNLOAD Not available for any layout
CATEGORY Any layout except repeating record layouts
CONTACT Any layout except repeating record layouts
DATE_CLOSED Read-only on the edit screen only
DATE_CLOSED_SINCE Reporting filters only
DATE_CODE_FREEZE Not available for any layout
DATE_CREATED Read-only on add and edit screens. Not to be used on repeating records
DATE_CREATED_DAY Not used on add screens, edit screens or repeating records. Only used for reporting purposes
DATE_CREATED_MONTH Not used on add screens, edit screens or repeating records. Only used for reporting purposes
DATE_CREATED_SINCE Not used on add screens, edit screens or repeating records. Only used for reporting purposes
DATE_CREATED_TRUNC Not used on add screens, edit screens or repeating records. Only used for reporting purposes
DATE_CREATED_WEEK Not used on add screens, edit screens or repeating records. Only used for reporting purposes
DATE_CREATED_YEAR Not used on add screens, edit screens or repeating records. Only used for reporting purposes
DATE_FIRST_CUSTOMER_SHIP Not available for any layout
DATE_LAST_STATUS_CHANGE Read-only on edit screen. Not used on add screen. Not to be used on repeating records
DATE_LAST_STATUS_CHANGE_SINCE Reporting filters only
DATE_RELEASE_TO_QA Not available for any layout
DAYS_IN_STATUS Reports only
DAYS_OPEN Reports only
HIST_RANGE_END May only be used as a filter on a search layout
HIST_RANGE_START May not be used on any layout. Only used in the CLI
ID Read-only on add and edit screens. Not to be used on repeating records
ITEM_ID Should not be used on any layout
LAST_CHANGE_USER Read-only on edit screen. Not used on add screen. Not to be used on repeating records
LAYOUT Not available for any layout
LAYOUT_TYPE Not available for any layout
MODULE_ASSIGNED This field is deprecated and should not be used
MODULE_DATE_CREATED This field is deprecated and should not be used
MODULE_ID Not to be used on repeating records
MODULE_NAME Should not be used on layouts
MODULE_PRODUCT This field is deprecated and should not be used
MODULE_STATUS This field is deprecated and should not be used
MODULE_TIMESTAMP This field is deprecated and should not be used
MODULE_TITLE Should not be used on layouts
MODULE_TYPE This field is deprecated and should not be used
MODULE_VERSION This field is deprecated and should not be used
MONTHS_IN_STATUS Reports only
MONTHS_OPEN Reports only
ORIGINATOR Any layout except repeating record layouts
OWNER Any layout except repeating record layouts
PRIORITY Any layout except repeating record layouts
PRIVACY Any layout except repeating record layouts
PROBLEM_RELEASE_ID Should not be used on any layout
PRODUCT_LINE Any layout except repeating record layouts
PRODUCT_NAME Any layout except repeating record layouts
PRODUCT_NAME_HIST Should not be used on any layout
PROJECT All Add and Edit layouts belong to a specific Project within a Business Area. If the PROJECT field is placed on the layout, then the field and its values will be presented in the normal way. If the PROJECT field is not placed on the layout, then ExtraView processes the layout as if the value of the Business Area is set to the same value to which the layout belongs. This helps the usability for many applications where there is more than one Project within a Business Area, but you want to restrict the user to only working within a single Project at a point in time. If you want to restrict the user to only being able to address a subset of the available Projects within a Business Areas, you may use the FIELD HIDE VALUES and the FIELD VISIBLE VALUES to restrict the displayed values.
RELATIONSHIP_GROUP_ID Should not be used on any layout
RELATIONSHIP_GROUP_OWNER Should not be used on any layout
RELATIONSHIP_GROUP_TITLE Should not be used on any layout
RELATIONSHIP_GROUP_TXNS This field is only valid on a layout of type HISTORY.
RELATIONSHIP_GROUP_TYPE Should not be used on any layout
RELATIONSHIP_GRP_PARENT_ID Should not be used on any layout
RELEASE Should not be used on any layout. The LAYOUT.RELEASE field may be embedded on the add and edit screens to support repeating records
RELEASE_ASSIGNED_TO Repeating records and reports only
RELEASE_DATE_CREATED Repeating records and reports only
RELEASE_DIRECTORY Should not be used on any layout
RELEASE_FIXED Repeating records and reports only
RELEASE_FOUND Repeating records and reports only
RELEASE_FOUND_HIST Should not be used on any layout
RELEASE_OWNER Repeating records and reports only
RELEASE_PRIORITY Repeating records and reports only
RELEASE_PRODUCT Repeating records and reports only
RELEASE_RESOLUTION Repeating records and reports only
RELEASE_SEVERITY Repeating records and reports only
RELEASE_STATUS Repeating records and reports only
RELEASE_TIMESTAMP Read only on repeating records and reports
RELEASE_TYPE Deprecated – do not use
REL_GRP_DATE_CREATED Should not be used on any layout
REL_GRP_TIMESTAMP Should not be used on any layout
RESOLUTION Any layout except repeating record layouts
SEVERITY_LEVEL Any layout except repeating record layouts
SHORT_DESCR Any layout except repeating record layouts
START_DATE Reports only. Note that the data dictionary setting “Filter criteria” must be set to Yes for this field to work
START_UPDATE Reports only. Note that the data dictionary setting , “Filter criteria” must be set to Yes for this field to work
STATUS Any layout except repeating record layouts
STATUS_HIST Should not be used on any layout
STOP_DATE Reports only. Note that the data dictionary setting “Filter criteria” must be set to Yes for this field to work
STOP_UPDATE Reports only. Note that the data dictionary setting “Filter criteria” must be set to Yes for this field to work
TIMESTAMP Read-only on add and edit screens. Not to be used on repeating records
TIMESTAMP_DAY Not used on add screens, edit screens or repeating records. Only used for reporting purposes
TIMESTAMP_MONTH Not used on add screens, edit screens or repeating records. Only used for reporting purposes
TIMESTAMP_SINCE Not used on add screens, edit screens or repeating records. Only used for reporting purposes
TIMESTAMP_TRUNC Not used on add screens, edit screens or repeating records. Only used for reporting purposes
TIMESTAMP_WEEK Not used on add screens, edit screens or repeating records. Only used for reporting purposes
TIMESTAMP_YEAR Not used on add screens, edit screens or repeating records. Only used for reporting purposes
WEEKS_IN_STATUS Reports only
WEEKS_OPEN Reports only

 

Data dictionary field name- LABEL field types Notes
CC_EMAIL Should not be used on any layout. This field is automatically added to the add and edit layouts with the notification fields
DELETE_BUTTON Reports only
EDIT_BUTTON Reports only. Note that this field is automatically added to any custom report
EMAIL Should not be used on any layout
FILTER_CHILD_VALUES Should not be used on any layout
GENERATE_EMAIL Should not be used on any layout. This field is automatically added to the add and edit layouts with the notification fields
HISTORY_BUTTON Reports only
KEYWORD Report filters only
PROBLEM Should not be used on any layout
RELATIONSHIP_GROUP_LINK Should not be used on any layout
REPORT Should not be used on any layout
REPORT_BY Should not be used on any layout
REPORT_NAME Should not be used on any layout
REPORT_OUTPUT Should not be used on any layout
REPORT_TYPE Should not be used on any layout
SORT Should not be used on any layout
VIEW_BUTTON Reports only. Note that this field is automatically added to any custom report

 

Data dictionary field name- SCREEN field types Notes
ADD_PROBLEM Should not be used on any layout
ADD_PROBLEM_SUMMARY Should not be used on any layout
ADMINISTRATION Should not be used on any layout
ATTACHMENT This is the field that places attachment records on add and edit screens. It can also be placed on detailed reports and Quicklists, but not on report filter layouts. Security permissions should be set for the individual fields such as ATTACH_FILE_NAME and ATTACH_FILE_SIZE to control their visibility
BATCH_COMMANDS Should not be used on any layout
COMPANY_NAME Should not be used on any layout
CUSTOM_EMAIL Should not be used on any layout
HOME_PAGE Should not be used on any layout
PAGE_SIZE Should not be used on any layout
PROBLEM_RELEASE_DELETE Should not be used on any layout
PROBLEM_SUMMARY_EDIT Should not be used on any layout
QUICK_LIST Should not be used on any layout
RELATIONSHIP_GROUP Should not be used on any layout
SEARCH_REPORT Should not be used on any layout
SECURITY_GROUP Should not be used on any layout
SECURITY_KEYS Should not be used on any layout
SECURITY_PERMISSION Should not be used on any layout
SIGN_ON Should not be used on any layout
STATUS_CHANGE Should not be used on any layout
SYSTEM_LOG_TYPE Should not be used on any layout
UDF Should not be used on any layout
USER_ACCOUNTS Should not be used on any layout

 

Data dictionary field name- SESSION and SPECIAL field types Notes
USER Should not be used on any layout
SYSDATE Should not be used on any layout