Release date: 2021-06-24
New Features
General UI
- Following the update, users will be required to reset their password once due to the migration to a new user database model. To reset, click the “Don’t remember your password?” An e-mail will be sent to the user address specified. Then follow the instructions in the e-mail.
- The user databases are shared between the kaizen and kaizen-east servers.
- This means that all users will have access to both severs.
- Changing a user password in one server will automatically change the password on the other server.
- The users will retain any permissions to clients and buildings they have in either of the servers.
- Reporting insight emails has been updated with content and timing. An email will now be sent every 4 hours if there are reports that have been generated within that 4 hour window. The email will contain a list of all reports organized by client and building. There will be a link in the email that connects to the report within the Kaizen UI. The email will no longer contain a PDF attachment of the report.
Bug Fixes
Insight Management
- Fixed an issue where Chinese characters were not being properly displayed when exporting a View to PDF format.
- Insight Management views will now appear properly.
Vault
- Import and Export of Trend Logs in the TL viewer are now functioning properly
- Weather Trend Logs are being displayed again.
- Export CSV for Trend Logs has been fixed and is again available for users.
Reporting
- (Graph based) Report emails are now being delivered as expected. The first email will contain a link for each of the reports that were missed during the downtime.
- Insight Subscription emails are being delivered properly.
- Removed Building Operator Report templates from the Community Library. This functionality has been replaced previously by the Insight Subscriptions.
- Building Operator Report – Equipment In Hand
- Building Operator Report – Schedules Changed
- Building Operator Report – Setpoints in Manual
General
- Updated version to the correct value of 3.6.8
API
- Resolved and issue where some get_tl_data_start_end api request were returning invalid data.