Skip to content

3.6.0 (2019-12-30)
Compare
Choose a tag to compare
@ndobb ndobb released this 31 Dec 01:21
· 130 commits to master since this release
v3.6.0
22cd4a2

This release adds a new administrative feature for searching for user's saved queries, as well as an optional new feature to automatically email administrators when users ask questions, along with a host of bug fixes.
image
image

New Features

  • #295 - Leaf administrators can now search for and open user queries by navigating to the MyLeaf window and "User Saved Queries" tab.
    image

  • #310 - Leaf can optionally use an SMTP server to automatically send an email to administrators when users have questions. This allows institutions to more easily track inquiries and create tickets from templated emails. Note that this features is 100% opt-in; if disabled, Leaf simply informs users of the configured administrator email.

Minor Features

  • #297 - Pressing Enter on the keyboard now closes the date and numeric filter modals. This was added for convenience, and these can still be set by simply clicking outside of the modal.

Numeric filter
image

Date filter
image

Bug Fixes

  • #299 - If a user logged out twice and attempted to log in again, the login would fail. This was due to a bug in how Leaf attempted to circumvent browser caching/SAML2 authentication failures (see issue for details).
  • #293 - REDCap imported projects now have metadata loaded on demand, rather than at login. This was not necessarily a bug, but this fix is designed to reduce heavy, unnecessary calls to the server as users login.
  • #292 - Very minor, but in the admin pane the 'Unsaved' and 'Delete' divs would sometimes overlap with content.
  • #291 - In the admin pane, concept updates would fail if the concept had any specializations defined.
  • #288 - In the admin pane, updating a concept's display text (the name, subname, or patient count) would fail to be properly updated.
  • #290 - The login modal now displays more helpful, detailed information if the initial user login fails for any reason.

Upgrading to 3.6.0

  • Client app and server API - Recompile and deploy the latest client and server API files as described in the Leaf installation instructions, making sure to first remove any previously deployed instances.
  • appsettings.json - Version 3.6 adds a few new entries to the appsettings file which must be added accordingly.
    • Notification
      • Enabled (boolean, if true, the below properties must be set)
      • Email
        • Server (string) - the SMTP server name.
        • UseSSL (boolean) - Determines whether Secure Socket Layer protocol should be used for transporting emails (we recommend setting this to true)
        • Sender
          • Address (string) - email address from which to send emails from.
        • Receiver
          • Address (string) - email address (e.g., list-serv) to receive send emails.
        • Credentials (optional, only if you'd like to use a username and password to authenticate with the SMTP server)
          • Username (string) - Username to provide the SMTP server. This should be LEAF_SMTP_USR, and you if this is defined, you must also set a corresponding environment variable to store the actual username.
          • Password (string) - Username to provide the SMTP server. This should be LEAF_SMTP_PW, and you if this is defined, you must also set a corresponding environment variable to store the actual password.

See the default appsettings.json for reference.

  • Database - execute the 3.5.0__3.6.0 database update script on your Leaf application database.
Assets 2
Loading