Release date:
🎃 Happy Spooky season ! 🎃
We’re committed to delivering updates more frequently to keep improving your experience. This release brings a series of enhancements across core platform features, Power BI, and Tableau Server integrations. From advanced deployment customization to simplified onboarding, each update is designed to make everyday tasks more intuitive and efficient.
🚀 We’re especially thrilled to introduce support for Tableau Server through Wiiisdom Gateway clients — a major milestone that unlocks secure, scalable, and seamless integration for enterprise environments.
📘Full Documentation: https://support.wiiisdom.com/documentation
👨💻Contact us via your Customer Centre and Support Site: https://support.wiiisdom.com/
Navigating through execution history is now easier thanks to new sorting options by status and start date. Whether you're reviewing scheduled tasks or monitoring ongoing executions, you can quickly organize the list to match your workflow.
Getting started on the platform is now quicker and smoother for new team members. When an administrator creates a non-admin account and SSO is configured, the new user automatically receives a welcome email with a direct link to log in via SSO.
The onboarding message is sent immediately upon account creation, helping teams stay focused on what matters most: establishing strong analytics governance from day one.
The Deploy Content (Cross Environment) step now offers full customization capabilities, allowing you to define report and dataset names manually, choose specific workspaces, and securely configure parameter values with encryption.
This enhancement ensures that deployments match your exact structure and naming conventions, while maintaining compatibility with existing options like content overwriting. This is available both in the interface and through the API, making it easier to integrate into automated workflows. Compatibility with existing options like content overwriting is fully maintained.
Customization details are also reflected in logs and reports, providing transparency and traceability throughout the pipeline design process.
Editing rules in a Dataset step using DAX mode now offers greater flexibility. A collapsible query editor has been introduced, allowing data engineers to temporarily hide the query panel and focus on the full configuration form.
This makes it easier to review and adjust settings without losing context or screen space. The feature is available while designing pipelines that include Row Count or Column Statistics steps, and is based on the same approach used in execution reports for advanced mode.
It’s a small change that brings a clearer, more comfortable editing experience.
When validating semantic models, selecting all tables at once can sometimes include measure-only tables—those without visible columns—which aren’t compatible with certain validation steps.
This update ensures that these tables are now automatically excluded from steps like Row Count, Dataset Statistics, Dataset Values, and Duplicated Rows.
Measure-only tables still appear in selectors but are disabled, with helpful tooltips explaining why they can't be selected. This makes it easier to build complete and accurate validation pipelines without manual filtering.
The change was inspired by real-world feedback and helps ensure that validation steps focus only on relevant, analyzable data.
It’s now possible to include the Open Report action directly in your pipelines using the API.
These steps can be added alongside existing deployment actions such as Deploy and Deploy Content Cross Environment. This enhancement allows for more flexible automation scenarios, especially when validating content as part of a deployment flow.
The “time threshold” parameter will be automatically rounded to the nearest tenth of a second, ensuring consistent timing without manual adjustments. Full implementation details are available in the API documentation page.
You can now promote paginated reports using the classic Deploy Content step, whether you're working in the interface or through the API.
This makes it easier for data engineers to move reports from development workspaces to shared environments, ensuring the right insights reach the right teams.
Paginated reports appear alongside non-paginated ones when configuring the step, and are fully supported during execution. Other steps—such as Regression Test, Open Report, Simulation Journey, and Cross Environment Deploy—remain focused on non-paginated content.
API support is also included: simply reference the paginated report ID in your payload, and it will be deployed as expected.
A new section called Wiiisdom Gateway is now available in the Admin menu, designed to support secure communication between Wiiisdom and Tableau Servers hosted in private networks.
This interface allows administrators to view all available clients, check their status, and manage credentials. Each client is identified by a unique ID and Secret ID, ensuring secure access.
Clients can be downloaded for Linux or Windows and will automatically restart after a server reboot. Once enabled, they allow the platform to run Extract, Regression, Promote steps and Version Management on Tableau versions 2024.2 and above. The configuration is seamless—BI platforms are set up using local URLs, making the integration transparent and efficient.
⚠️ Limitation in the initial release:
These limitations are scheduled to be addressed in future updates.
▪ With Regression Test (Different Report) and Regression Test(Cross Environment), reports with RLS end in Technical Error (Impact: Medium)
Description: If you use Regression test (Different report) or Regression test (Cross environment) steps to test a report that has RLS with multiple roles, even if your user is properly assigned to a role, the pipelines ends in Technical Error. This does not affect Open Report, Simulation Journey or Regression test (Same report).
ID: WIIIS-2103
▪ Recurring paused executions will not resume when a pipeline is reactivated, and no new recurrence is created (Impact: Low)
Description: If a recurring pipeline is in “pause” state when the time to trigger happens, it is never rescheduled even if you reactivate it.
ID: WIIIS-2083
▪ New schedule creation is blocked due to previous execution issues (Impact: Low)
Description: If a recurring pipeline was disabled when the scheduled time happens, it does not get rescheduled once it is reactivated.
ID: WIIIS-2089
▪ Context list of predictive scoring is not properly displayed if your screen is 1920 px wide (Impact: Low)
Description: Context list of predictive scoring is not properly displayed if your screen is just under 1920 px wide.
ID: WIIIS-2113
