Release date:
This release introduces reusable rule templates for BI Policies Enforcement across Power BI and Tableau, adds support for Fabric Org Apps in Deploy Content for Power BI, and extends Tableau testing with new regression checks and new Simulation Journey assertions.
As always, you can find important links just below.
📖Full Documentation 💡Knowledge Base 📞Customer Support
A single rule set rarely fits all your content. Certified or governed reports and dashboards usually need stricter checks than standard or exploratory ones, and applying the same rules everywhere either over-constrains one group or under-protects the other.
Administrators can now define multiple rule templates for Power BI and Tableau. Pipeline designers select the template to apply on each BI Policies Enforcement step, and the template used is shown in the execution report.
The default template is also the one used for the insights and recommendations in Predictive Monitoring.
Critical actions in Wiiisdom Cloud Platform now generate audit events, giving administrators a clearer trail of who changed what.
Audit events are now recorded when Predictive Scoring is activated or deactivated on a BI Platform, when its Runners are updated, and when a workbook version is downloaded or restored using Tableau Version Management.
You can now create and update pipelines containing a Dataset Values step for Power BI or an Extract Values step for Tableau through the public API.
Pipelines with these steps can also be generated through our MCP. Columns and tables are identified by name rather than technical ID, so they are easy to reference without digging through the platform.
The Runner configuration diagnostic introduced in the previous release now performs additional validations. It goes further on workspaces, including those holding Microsoft Fabric Capacity Metrics, and on permissions-related requirements.
More configuration issues are now caught during setup, with clear, readable messages and warnings for non-blocking issues, rather than after go-live.
The AI-powered recommendations introduced for Tableau in the previous release now extend to Power BI. When a page fails the Render Duration policy in a Report Policy Enforcement step, you get recommendations on what to change to bring it under the limit.
Recommendations are generated when the pipeline runs, only for the pages that failed, and ranked by importance so the most impactful changes come first.
Deploy Content can now include Fabric Org Apps, the items used to package Power BI content for your consumers. They appear in the Deploy Content configuration tree, are deployed when the step runs, and are listed in the execution report.
Org App audiences linked to the source Org App are also duplicated to the target workspace, so the app arrives ready to use.
Note: if you already have Power BI configured, an extra step is needed before you can use this capability, as the app registration in Microsoft Entra ID requires a new API permission, which you can refresh from Wiiisdom Cloud Platform or grant manually in Entra.
The Simulation Journey step is now fully supported in pipelines for Power BI tenants connected through the Wiiisdom Cloud Platform Gateway, including tenants restricted to internal networks, matching its behaviour in the standard cloud connection.
With this addition, every pipeline step now runs through the Wiiisdom Cloud Platform Gateway, giving full pipeline parity between the standard cloud connection and Gateway-connected tenants.
Regression Test (Cross Environment) for Tableau gains two more non-visual checks, building on those introduced in the previous release: filter values and filter domain values. They compare the values selected in each filter, and the values available in it, between your source and target workbooks.
The execution report details now show the filter results, including differences in each filter's existence, data type, values and domain values, so you can see exactly which filter change caused a regression. You can also compare the allowable values of a parameter between two workbooks.
Simulation Journey, introduced in the previous release, gets two new assertion sub-steps: Assert Filter Equals and Assert Parameters Equals. They let you verify that a filter or a parameter in your view has the value you expect.
As with the other Simulation Journey steps, you can ask the AI assistant to create them for you in plain language.
▪ Faster Tableau Policy Enforcement
Policy enforcement on Tableau Server now runs in parallel, reducing execution time.
▪ Admin-Managed pipelines
Pipelines now show an Admin-Managed badge, with a warning on the Service Principal property. Run now and scheduled runs execute only on the intersection of the user's rights and the Runner's rights.
▪ More accurate Duplicate Content Detection findings
Findings that no longer reflect your Power BI tenant, for example because a report was deleted or is no longer a duplicate, are no longer shown. When the set of duplicate reports changes, a new finding replaces the overlapping one, and the reason is recorded in the agent audit.
▪ Simulation Journey step status has no impact on the pipeline status
High impact · WOFT-3509
Description: A Tableau Simulation Journey step could end in success even when one of its sub-steps had failed.
▪ Multiple Simulation Journey steps in one pipeline execute the first step repeatedly
High impact · WOFT-3478
Description: When several Simulation Journey steps were configured in the same pipeline, only the first step was executed and it was displayed repeatedly in the execution report. This has been resolved.
▪ Regression test stuck in running status with a technical error
High impact · WOFT-3477
Description: Regression tests on certain Tableau workbooks could remain in a running status and show a technical error, even though all validation checks had completed successfully.
▪ Simulation steps may hang on functional reports
Medium impact · WCPC-405
Description: Some Power BI reports containing hidden visual groups always ended in a timeout in Open Report, Simulation Journey and Policy Enforcement steps.
▪ Error status on Workbook Policy enforcement without a technical error
Medium impact · WOFT-3489
Description: In some specific cases, the Workbook Policies enforcement step ended with an error status even though no technical error had occurred.
▪ Bulk delete in the pipeline list not fully clickable
Low impact · WCPC-305
Description: The bulk delete control in the pipeline list was not fully clickable. This has been resolved.
