Initializing help system before first use

The Lifecycle of Scenario Data

A scenario persisted in FICO® Xpress Insight can have input data, results data, and file attachments. A scenario is created in an unloaded state with no input data, no results data and no file attachments.
The usual way of transitioning the state of the scenario data is to execute the scenario. There are two types of execution mode:
  1. One which sets the input data. This load type of mode has the clearInput flag set to true. On execution of a scenario with this type of execution mode, any existing input data values will be erased. When the model exits, Xpress Insight will capture and persist the current values of the input data entities.
    Note: The built in LOAD execution mode has clearInput=true.
  2. One which sets the result data. This run type of mode has the clearInput flag set to false. On execution of a scenario with this type of execution mode, the input data entities in the model are initialized to their values as stored by Xpress Insight with a call to the insightpopulate function. When the model exits, Xpress Insight will capture and persist the current values of the result entities.
    Note: The following information should be noted:
    • The built in RUN execution mode has clearInput=false.
    • Existing result data values are erased on any execution mode.
    • Input entities can be re-captured during a run type execution by annotating them with @!insight.update.afterexecution true.
    • You can still rename, move, clone, or delete a scenario that is reserved for a job.
For more on execution modes, see the later topic on Mosel Execution Modes.
The result data for a scenario should be consistent with the input data. The system provides three options for how the results data is treated as the input data evolves:
  • On-change—the result data is deleted as soon as an input entity value is modified.
  • On-queue—the results data is flagged as dirty as soon as an input entity value is modified, and deletion of the result data is deferred until the scenario is queued for execution.
  • On-execute—the results data is flagged as dirty as soon as an input entity value is modified, and deletion of the result data is deferred until the scenario begins executing. These options can be set via a global Mosel annotation insight.resultdata.delete=[option].
Parent Topic The Model and Scenario Data Management

© 2001-2023 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.