Initializing help system before first use

# Adding an Execute Button

With VDL Actions, you can add a button to a view that allows a user to submit a scenario for execution with a given execution mode, optionally setting a scalar entity first. For more, see Model Execution using VDL Actions.

By default, a button that initiates scenario execution will trigger the first scenario by default and set the execution mode to RUN.

View Designer

In the Palette > Actions group, click and drag an Execute Model element onto the Section.

In the Palette > Components group, click and drag a Button element onto the Column. In the Button > Attributes > Events pane, click Add Event. Configure the Event:

- Set the Event to click.
- Set the Action Group to actions.action_group_1.

To change the scenario, select the Execute Model action and update the Data > Scenario setting:

View Designer
Figure : 1. Adding a button in the View Designer

To change the execution mode, select the Execute Model action and update the Main > Mode setting: You can set the mode to be any custom execution mode defined in the model, or one of the standard modes(LOAD and RUN).

It is good practice to set a scalar before execution. The `value` attribute accepts an expression so you can calculate the value based on the current values of other model entities.

    <vdl-button vdl-event="click:actions.action_group_1" entity="LIMIT" value="=getLimit()" caption="Evaluate limited dataset">
    </vdl-button>

Parent Topic Exploring the Core Components

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.