forio Toggle navigation

v1.34 Release Notes

Release Date: 10/27/2015

Updates and Improvements

  • Automatically bring runs from the database into memory.

    Runs must be in memory in order for you to update variables or call operations on them. (See more information on run persistence.)

    In previous releases, a run that had been removed from the current session had to be explicitly replayed in order to bring it from the database back into memory.

    New in this release, runs are automatically replayed whenever you attempt to update variables (PATCH) or call operations (POST).

    Additionally, you can optionally replay a run, bringing it into memory, whenever you look it up (GET). To replay on GET requests, add a header to your request.

    You can control the behavior for PATCH, POST, and GET in your model.cfg file by including your autoRestore preference. (See more on model configuration files.)

  • Copy decisions from one run to another when cloning runs.

    You can now use the Model State API to clone a run (that is, make a new run based on an existing run) AND specify that only the final values of the decisions and variables are copied to the new run.

    The typical use case is an end user interacting with a project and advancing a run to completion — for example, changing interest rates repeatedly and watching the total investment values change over time — and then wanting to "play again" starting with the final decisions from the previous run. This is most common for SimLang and Vensim models.

    To clone a run and have only the final values of decisions copied to the new run, specify in the clone request that you want to exclude the operations that advance the model. See more information and details of the API call.

Notable Bug Fixes

  • The Support Forum now correctly detects whether or not you are already logged into the Epicenter authoring interface.
  • Improved error messages for some of the REST APIs.
  • Several minor fixes for performance and stability.