Epicenter Release Notes: v1.41 | Documentation

v1.41 Release Notes

Release Date: 8/10/2016

Interface Builder (Alpha). We are piloting a new Interface Builder within Epicenter. You can use it to create a user interface for your project based on provided templates. The Interface Builder is currently in an Alpha release, works best with Vensim projects, and is available for new projects only.

Once it is more full-featured, the Interface Builder will replace the existing UI Builder. In the mean time, feel free to send us your feedback as we continue with the Interface Builder development! Of course, you can always use any of the Epicenter APIs to create your project interface as well.

Self-Registration for End Users. In previous releases, there were two ways to add end users to groups: add them manually one by one, or upload a spreadsheet.

New in this release, you can now have end users register themselves. The advantage of self-registration is that end users can enter their own personal information (name, password) rather than having you enter this information on their behalf.

After enabling self-registration for your project, you can choose whether to require users to be pre-approved or not. Requiring pre-approval means only usernames matching email addresses that you specify can successfully register; otherwise, anyone can register as an end user in your project if they have the self-registration URL. See the complete details on setting up self-registration for your project. Remember that some Epicenter subscriptions have limits on the number of end users per authenticated project.
Tracking Runs for Anonymous Users. The run record has a new, optional, field: scope.trackingKey. This field is searchable, and can be set to any string. You can include it when creating a run as an easy way to keep track of all runs associated with a particular user, even if that user is "anonymous" (that is, your project access is public and the user has not logged in).

As part of the new feature self-registration feature described above, the Password API now requires a redirectUrl, to which end users are directed after resetting their password. It also supports customization of the subject line of the password recovery email. This means that end users can receive customized emails, specific to your project, when they request to reset their passwords.