Release date:
🍂Happy Autumn Everyone! 🍂
This update brings meaningful improvements across scheduling, session management, and BI integrations. Whether you're optimizing pipeline execution, securing user sessions, or managing content across Power BI and Tableau environments, this release is designed to make your workflows smoother, safer, and smarter.
Full Documentation: https://support.wiiisdom.com/documentation
Of course, do get in touch if you need help with updating.
Contact us via your Customer Centre and Support Site: https://support.wiiisdom.com/
Previously, scheduling recurring pipeline executions offered limited options, making it difficult to align test runs with specific operational rhythms.
This update introduces a more detailed scheduling system, allowing configuration by minutes, hours, days, weeks, or months. It also includes a new "Execution Window" setting to restrict execution to specific days and time ranges (e.g., weekdays between 8 AM and 5 PM).
Each configuration clearly displays the next scheduled run, helping ensure better control and predictability.
Coordinating recurring executions across different regions can lead to confusion when relying solely on UTC timestamps. With this update, it’s now possible to select a time zone during configuration.
While all executions are still scheduled using UTC as the reference, the interface now clearly displays the corresponding local time based on the selected time zone. This makes it easier to understand exactly when tasks will run in your context, reducing ambiguity and improving planning accuracy.
In addition to recurring schedules, it’s still possible to configure a pipeline to run just once at a specific time. For even more advanced scheduling scenarios, the Scheduling API remains available, allowing you to define complex execution logic programmatically and integrate it into broader automation workflows.
Finding and managing pipeline executions could be tedious, especially when trying to review results or make quick changes.
The new execution list interface introduces a cleaner layout with essential details like status, start time, and duration displayed upfront. Sorting and filtering options make it easier to locate specific runs, while multi-selection and bulk deletion simplify cleanup.
A direct shortcut to edit the pipeline is now available when appropriate, reducing the need to navigate across multiple views.
This update brings clarity and efficiency to execution monitoring and management.
Managing active sessions across devices could be challenging, especially after a password change or when needing to secure an account quickly.
This update introduces a dedicated session management page that allows viewing all active sessions and revoking them individually or all at once—including the current one. Additionally, when changing a password, there’s now an option to automatically close all other sessions.
Administrators also gain a new action to close all sessions and revoke personal access tokens for any user directly from the user list. These enhancements provide more control and transparency over account activity.
Deploying across Power BI tenants is now more flexible. You can manually configure report names and workspaces, giving you greater control over how content is published.
To support scalable and automated workflows, a new deployment API is available. This enables seamless integration into your CI/CD pipelines, making cross-tenant publishing more efficient, secure, and enterprise-ready.
A new tab in Tableau Versioning now shows all calculated fields—including name, formula, type, and view—making it easier to track logic changes across versions. You can also export this data to Excel for deeper analysis or documentation.
This feature supports organizations subject to EUC (End User Compute) regulations by automatically surfacing critical metadata, improving traceability and reducing manual effort in compliance reporting.
Comparing dashboards across different Tableau environments used to require manual workarounds, especially when validating content consistency between development, staging, and production.
This new step simplifies the process by enabling automated regression testing between sites. It allows selection of multiple workbooks and offers flexible mapping to target projects and workbooks, either automatically or manually.
The comparison logic is consistent with existing dashboard-level regression tests, and results are presented in a familiar report format.
This addition enhances confidence in cross-environment deployments while retiring the older “Different Dashboard” step.
▪ We’ve enforced TLS v1.3 across all API endpoints to ensure stronger encryption and better performance. Older TLS versions are no longer supported, aligning with modern security standards and protecting your data in transit.
▪ Execution services are now more resilient and controllable. A new queuing mechanism ensures smoother handling of concurrent runs, and you can now manually stop pipelines, giving you more control during troubleshooting or unexpected behavior.
▪ To prevent confusion and improve traceability, pipelines must now have unique names. This eliminates accidental overwrites and makes it easier to manage and audit your automation flows.
▪ We’ve enhanced the Tableau URL validator during BI Platform setup to catch misconfigurations early and guide users through a smoother setup process. This reduces onboarding friction and ensures reliable platform connections.
▪ Pipeline reports now automatically retrieve and display the actual metadata stored in Tableau or Power BI, rather than relying on manually entered values. This ensures greater accuracy, consistency, and trust in the information presented during execution.
▪ The Tableau simulation engine now supports domain-restricted Connected Apps, enabling more secure and controlled integrations. This enhancement ensures that only apps from approved domains can interact with your simulations, improving compliance and reducing risk.
▪ Impossible to take a version of heavy workbooks in TVM (Impact: Medium)
Description: If you have a workbook that is several gigabytes in size, it won’t be versioned.
ID: WOFT-3003
▪ Scanner list is stacked (Impact: Low)
Description: Scanner list does not respect Wiiisdom graphical chart.
ID: WOFT-2525
▪ Pipeline names are capitalised in their reports (Impact: Low)
Description: Pipeline names are capitalised in their reports.
ID: WOFT-2158
▪ In the user list page, buttons are not aligned to the right of the table (Impact: Low)
Description: If enforce SSO policy is enabled, the action buttons in user list are not properly aligned.
ID: WIIIS-2087
▪ Duplicate entries for Power BI Reports, Datasets and Tables in Predictive Scoring (Impact: Medium)
Description: After multiple runs of Predictive scoring, if you have multiple tenants you have duplicated content in the scoring list. Global insights are not impacted.
ID: WIIIS-2080
▪ Power BI Predictive Scoring loader consume too much resource (Impact: Medium)
Description: Randomly, Predictive Scoring PBI data loading exhausts database connection pool, impacting other services availability.
ID: WIIIS-2043
▪ Cannot enter multiple emails in post process (Impact: Low)
Description: If you enter multiple emails in post process configuration and then click on save an error tells you it must be a comma-separated list but the interface does not accept such a list.
ID: WIIIS-2057
▪ Invalid time displayed when configuring Predictive Scoring on a BI Platform (Impact: Low)
Description: The daily extraction time in Predictive Scoring configuration wizard does not properly take your time zone into account and gives inconsistent results.
ID: WIIIS-2020
▪ Duplicated objects listed in the Predictive Scoring insights (Impact: Low)
Description: Duplicated objects listed in the Predictive Scoring insights.
ID: WIIIS-2018
▪ Global average daily refresh compute metric is far too low in the Semantic Model daily refresh compute Power BI insight (Impact: Low)
Description: Global average daily refresh compute metric is far too low in the Semantic Model daily refresh compute Power BI insight.
ID: WIIIS-2017
▪ In execution list, all executions stay in running until refresh, except the last one (Impact: Low)
Description: In execution list, if you launched your pipeline twice, you need to manually refresh the page to see the status change for the older execution.
ID: WIIIS-1994
▪ When we delete one execution of a pipeline with Simulation Journey or Open report step, the screenshot stays in ABS (Impact: Low)
Description: If you delete only one execution of a pipeline with Open report or Simulation Journey step, the screenshots are not deleted from ABS and therefore do not release space.
ID: WIIIS-1969
▪ Duplicate a pipeline multiple time lead to infinite pipeline label (Impact: Low)
Description: If you duplicate a pipeline, then duplicate the new one and so on, the pipeline label becomes so long the pipeline cannot be updated.
ID: WIIIS-1538
▪ "Actions related to the pipeline are pending" tooltip appears even when everything is ready on the Delete Pipeline Button (Impact: Low)
Description: When you want to delete a pipeline, a tooltip appears and tells you to wait. This tooltip should only appear when a baseline is being taken, not every time.
ID: WIIIS-1446
