Update to Forio Epicenter (1.49)

#1

Hello Everyone,

We’re excited to announce our latest updates to Epicenter.

This release of Epicenter includes several new features and improvements:

  • Full support for Simulate models. In particular, you can now create a project in Epicenter, upload your Simulate model (.eqn file), and use the Interface Builder to create a UI for your project.

  • Team members in both author and customer support roles can now impersonate end users in projects created with Epicenter.js 2.1 or higher. Impersonating an end user can help answer support questions from that user.

  • End users in the same group can now view each other’s runs. For example, this means that the user interface for a project can show a leaderboard, with the “top score” (a model variable) from every run visible to all end users in the group.

Complete release notes are below. As always, Epicenter release notes for this and other releases are available at: https://forio.com/epicenter/docs/public/releases/

Happy modeling!

WILL

v1.49 Release Notes

Release Date: 4/29/2017

New Features

  • Improved Forio SimLang Support. The Interface Builder now supports Forio SimLang models (.eqn files). Additionally, Epicenter now supports Forio SimLang models in the current version of our APIs: Epicenter.js 2.0 or later, v2 REST APIs. (In previous releases, Epicenter only supported Forio SimLang models in the older version of our APIs: Epicenter.js 1.8.1 or earlier, v1 REST APIs.)

  • Support Feature: Impersonate an End User. Impersonation is available for team members who have a role of author or customer support. Impersonation allows these team members to log in to a project as if they were an end user of that project. This can be useful for answering support questions from end users. Details.

Improvements

  • End users in the same group can now view each other’s runs, if they know the run id. In particular, end users in the same group can view variables from each other’s runs. For example, this means that the user interface for an Authenticated project can show a leaderboard, with the “top score” (a model variable) from every run visible to all end users in the group.

    As in previous releases, end users cannot update runs created by other users, unless the end users are all part of the same multiplayer world.

  • Some fields of the run record may now be updated for multiple runs at once. For the special case of the run record fields saved, closed, and trashed, you can update these fields for multiple runs at once. This is primarily useful for Run Comparison projects.

Bug Fixes

  • Error messages, particularly from the Run API, have been significantly improved.

  • Team members can explicitly set the active flag for end users in their projects to false by updating the user record via API. Those end users can then no longer log in to the project. (In previous releases, an explicit database update was required to update the active status, so this functionality was not available to team members.)

  • Other minor fixes for performance and stability.

#2