| Field Name | Title | Definition |
| DELETE_BUTTON | Delete Button | The item delete button. Access to the security permissions for this button allow users to delete issues |
| EDIT_BUTTON | Edit Button | The drill down edit button used on reports and within email |
| HISTORY_BUTTON | History Button | The button that accesses history from the edit screen or reports |
| QUICKEDIT_BUTTON | Quickedit Button | The button that accesses the Quickedit mode from column reports and Quicklists |
| VIEW_BUTTON | View Button | The drill down button that allows you to see the detailed report for an issue |
If you define a field with a display type of Custom in the data dictionary, and its name begins with the characters BUTTON_ or ends with the characters _BTN, a button will be generated on the screen, when you place the field on a layout.
The following are used to define the button:
| Data dictionary field | Purpose |
| Name | This defines the name of the field. For example, a button named BUTTON_GENERATE is valid. |
| Display Type | Must be Custom |
| Title | Typically this is a space character |
| Help Text | This will become the text on the button |
To provide the action for the button, place a layout cell attribute of type FIELD HTML MODIFIER within the layout upon which you place the button. For example, if you want to open a new window that displays an add issue screen, your FIELD HTML MODIFIER may look like this:
onclick=window.open("evSignon?p_action=doAddDisplay&p_option=Display&p_close_win=true&ev_menu=off&p_area=7&p_project=9")
Note that the URL does not need to reside within ExtraView. See the API Guide for more information.
Alternatively, you can provide an action for the button by implementing custom code within the class named ucRenderEmbeddedObject. The standard distribution of ExtraView that ships with the user custom class named CustomCodeBase.java contains this functionality.
