ExtraView has the ability for administrators to configure buttons and to place these on the output of Column, Detailed, Quicklist and Treegrid reports.
Each button that you configure is placed on a single row of the report output, and be similarly visible to the View, Edit and Quickedit buttons. The buttons are visible within the report editors and Design Center so the end user can select and place the button on any of the supported report types.
The report buttons have the ability to perform a single action that is applied to the issue on the row of the report. This action will use the name of the button to execute one or more business rules. For example:
if (MY_BUTTON.{changed}) {
STATUS = ‘Open’;
ASSIGNED_TO = BSMITH;
}
All button actions imply an update (or attempted update) to the issue on that row of the report output.
You define report buttons within the Data Dictionary tab named Labels / Buttons. On the Add or Edit screen for the button, select the Allow selection on reports option. This results in the button being available within report editors and within the Design Center for Quicklist and Detailed report layouts. Make sure you select an icon to display on the report output.
This example assumes you are going to immediately perform an update when clicking the action button on the report output. This example will alter the Status of the issue to Open and will assign the issue to a user with the user ID BSMITH.
if (MY_BUTTON.{changed}) {
STATUS = ‘Open’;
ASSIGNED_TO = BSMITH;
}
Column Reports and Treegrid reports are supported.
All report buttons that have been defined and to which the user’s role has permission appear within the list of buttons in the field selector. The field’s title will be used to identify each action button.
Report buttons are identified by being Buttons with a display type of Report Button. This will allow them to be placed on Detailed and Quicklist report layouts, and any layout that may embedded within these.
After the user runs the report and clicks the button on the output, the rule block associated with the button is executed and the issue updated.
It is possible that there is a dependency on the update that prevents the update happening. for example, there may be a missing required field value as the results of a REQUIRED IF operation or some business rule that prevents the update from continuing. When this occurs, the user will see a popup seeking the required field to resolve the conflict. Assuming this is provided correctly, the update will continue.
