Skip to main content

Release Notes: Version 25.12

What's New ✨​

Send emails from the rule framework​

A send_email function has been added to the rule framework, which allows users to send emails from rules. To find out how, check out our knowledge base by searching "Sending Emails" or by navigating to Platform > 3- Data Processing > Custom Business Logic > Custom Rules > 7- Sending Emails.md

Trigger schedule supports JSON output​

Trigger schedules can now also output json files. To do that, you can add the property "format" and set it to "JSON". More details are available in the trigger schedule documentation

ewx-cli self-service authentication​

The ewx-cli tool has been updated such that the authentication no longer requires the help of the Service Desk team. Users are able to authenticate themselves, through the Settings page in the new console.

⚠️BREAKING CHANGE ⚠️

  • Existing authentication with the cli will no longer work, when running the ewx-cli the next time you will be prompted to reauthenticate.
  • Please note: The ewx-cli now supports using the subdomain from the platform URL to identify the project. While old project names are still supported, using the subdomain is the preferred method.
    • For example, if your platform URL is test-t.energyworx.net, you can use test-t/enrx_org_001.
    • Similarly, for test.t.energyworx.net, you can use test.t/enrx_org_001.

Notable Improvements & Fixes 🛠​

🖥️ UI improvements​

  • Process Monitoring: Process Monitoring is now available through the original console and no longer needs Beta features enabled to be accessed.

  • Boolean Display Consistency: Booleans now read as True/False instead of Yes/No in the original console. This means that a tag property that is a boolean will now correctly display True instead of Yes. (Note: this is only a front-end change and does not impact rule implementation).

  • User-Friendly Task Configuration: Improved the task configuration page to show more user-friendly wording in the original console.

  • Clearer Rule Saving Warnings: When saving a rule, the warning message now specifies which fields require updating the flow, making it clearer to users when this use case applies.

🐛 Error Handling​

  • Improved Live Flag Validation Feedback: Corrected an issue where the system silently failed on saving invalid Live Flag configurations. The platform now implements proper validation feedback, ensuring that users receive a descriptive error message specifying the configuration conflict.

  • Datasource Audit Events: Fixed issue which prevented an Audit Event from being logged when a user accessed a datasource in the new console. This corrects an issue with traceability and now allows audit events to track any user that accesses a datasource, regardless of which console they use.

  • Improved DPA/Annotation Error Logs: Improved error log when saving DPA or annotations using store_timeseries. The message now specifies clearly what the issue is, making it easier for the user to correct the code.

⚙️ Platform & Backend Improvements​

  • Flow Property Lists: It is now possible to pass lists as values within flow properties.

  • Datasource Handling Standardization: Standardized datasource handling in the rule framework. This backend change cleans up the usage of legacy components in our processing, which will streamline and standardize the backend and make it easier to fix errors and develop new features in the future. (Note: This is a backend change with no impact on the end-user).

  • FlowCancelException Fix: Fixed an issue which prevented the show_exception_as_warning parameter to work when imported from the energyworx module.

🔐 API & Permissions​

  • Channel Family API Permissions: Fixed a permission issue in APIv2 where the system incorrectly checked for the "datasource" permission for Channel Family resources. Access is now correctly granted through the dedicated "channelfamily" permission.

25.12.01​

Bug Fixes​

  • Fixed issue where sign in provider would be wrongly set to Google for new users. It now respects the sign in method used.

25.12.02​

Bug Fixes​

  • Corrected cleanup logic to ensure Docker images remain, as long as they are being used by active workloads.

25.12.03​

Bug Fixes​

  • Fixed Frontend bug: Fixed an issue regarding the google analytics API, that was causing the Frontend Build to fail