Release date:
This release is mostly about security and governance — Runners, regulatory retention, and a cleaner experience based on what your license actually includes. There's also a solid batch of new policy rules for Power BI and Tableau, plus a handful of bug fixes.
📖Full documentation 💡Knowledge base 📞Customer support
Runners provide a dedicated service identity built around least-privilege and Zero-Trust principles, enabling secure execution of advanced features like Predictive Scoring.
Administrators can configure one or multiple Runners per platform, specifying credentials such as Application ID and secret for Power BI. Each configuration can be validated with a connection test before going live.
Predictive Scoring can then be activated directly from the Runner setup. Existing manual platforms continue to work as before, but creating new ones manually is no longer available.
Navigation menus now adapt to your subscription and permissions. What you see is what you actually have access to.
Administrators can check Platform Settings at any time to see exactly what their platform is licensed for.
For GxP and similar regulatory use cases, an immutable retention policy can now be enabled at the platform level. Contact Support to activate it. Once on, retention rules apply immediately to all pipelines and execution reports.
Retention clocks are based on pipeline update and report creation dates. While a retention period is active, deletion actions are visible but disabled, with clear messaging explaining why. Once expired, authorized users can delete items manually.
The Gateway configuration page now supports Power BI connections enabling secure interaction with Power BI tenants under restricted access.
Note that reports and datasets larger than 1 GB are not yet supported in this setup.
Available in the Report Policy Enforcement step, this rule checks whether custom visuals are present in Power BI reports and whether that aligns with your governance policies and security.
Configure it under Power BI settings in the Performance category. The validation report shows results per report, including the visual name and its expected status (Allowed or Forbidden).
Available in the Workbook Policy Enforcement step, this rule evaluates the loading and rendering time for each view within Tableau workbooks.
It sits in the Performance category, is set as Blocker severity, and defaults to a 10-second threshold.
The validation report shows measured rendering time and compliance status per view.
This rule checks the proportion of hidden fields within Tableau workbooks. It is in the Performance category, set as Best Practice severity, and defaults to 80%.
The validation report shows the percentage of hidden fields per workbook and their compliance status.
This rule monitors the number of Level of Detail calculated fields within Tableau workbooks. It is in the Performance category, set as Best Practice severity, and defaults to a threshold of 6.
The validation report shows the count of LOD calculations per workbook and their compliance with the defined rule.
API created pipelines can now include a Extract Refresh step to ensure reports are validated for functionality and performance before deployment.
The step supports a configurable duration limit. Only one field can be set at a time (days, hours, or minutes), and each value must be between 1 and 999.
To comply with ASVS, notifications are now sent per user rather than as bulk emails, reducing exposure risks associated with group distribution.
📦Pipelines in error now show an Advanced diagnostics button in the execution report, letting you download a ZIP with investigation details while excluding sensitive data.
▪ Metric Score cards appearing in Open report selector
High impact · WCPC-125
Scorecards were listed in the report selector for steps that do not support them (simulation, policy enforcement, non-regression).
▪ Inconsistent results for Design Policy Enforcement on PBIR reports
Medium impact · WIIIS-2285
Running the step on PBIR reports could produce null visual names or technical errors in the result display.
▪ Deploy content step showing technical error for paginated reports
Medium impact · WIIIS-2282
Successful deployments of paginated reports were incorrectly marked as failed.
▪ Step order changes when clicking after switching apps
Medium impact · WCPC-108
Clicking directly on a pipeline step after switching from another application could reorder steps unexpectedly.
▪ Duplicated Row step stays invalid after back navigation
Low impact · WIIIS-2270
Using the back button after configuring a Duplicated Row step could leave it in an invalid state in some cases.
▪ "Mark as read" disabled after refreshing notification center
Low impact · WCPC-124
Refreshing the notification center page could unexpectedly disable the "Mark as read" button.
