Initializing help system before first use

Understanding Execution Modes

Every scenario execution initiated by Xpress Insight has an associated execution mode.

Execution modes are defined in models using Mosel annotations—when the model is run, it can test for the execution mode and make predicate-based decisions.

Every app is assigned (and must implement behavior for) two standard execution modes— LOAD and RUN—that have constants associated with them in the model:
  • INSIGHT_MODE_LOAD
  • INSIGHT_MODE_RUN

These are used in a case statement in the example project to switch branching logic via the execution mode—in this case, to either load input data or populate Xpress Insight.

A model can also define any number of additional custom execution modes—they can offer your app two additional forms of control:
  • Executing different model code paths based on the execution mode selected by a user.
  • Routing different kinds of Xpress Insight jobs to different worker resources configured on the server. For example, you could have a model that performs small, fast jobs as well as large, slow jobs. Using custom execution modes, you can route the two different kinds of jobs to the worker resources best equipped to serve them.
Covered Topics
Parent Topic Building an Xpress Insight App

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