Release date:
☀️Happy Summer Everyone!☀️
We have been working towards supporting you in complying with GxP and other regulations!
As always, you can find important links just below.
Full Documentation: https://support.wiiisdom.com/documentation
Download Site: https://support.wiiisdom.com/downloads
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/
Disabling a user account on the Wiiisdom Cloud Platform was previously not possible.
To address this, we implemented a new action that allows administrators to disable user accounts, which also disables all associated schedules. Additionally, administrators can enable disabled user accounts, reactivating their schedules.
We also introduced a filter in the user list to display only enabled or disabled users, and tuned the pagination options for better usability.
This enhancement improves user management, enhances security, and provides a more streamlined administrative experience.
Connecting to on-premise applications using firewalls or strict network configurations was previously not possible, leading to difficulties in network configuration and troubleshooting.
To address this, we added a new menu item called "IP Settings" in admin mode, which provides a page with disabled text fields to copy the outgoing IPv4 and IPv6 addresses.
Additionally, tooltips were added in the Scheduling and Web Request Post Process sections to guide administrators in ensuring proper network configuration.
This enhancement improves network management, simplifies troubleshooting, and ensures seamless integration with the Wiiisdom Cloud Platform.
When deleting a BI Platform, if it was linked to BI Contexts or Scanners, the deletion would still go through, resulting in loss of data and operational disruptions.
To address this, we implemented a protection mechanism that prevents administrators from deleting these platforms if they have linked Pipelines or Scanners.
This enhancement ensures data integrity and operational continuity, providing a more secure and reliable experience on the Wiiisdom Cloud Platform.
Effective security measures are crucial, and enforcing SSO connections significantly enhances protection.
To address this, we implemented a policy that blocks any login attempts using username/password credentials for non-administrator users and prevents credential reset requests for these users.
This enhancement strengthens security and ensures that only authorized administrators can access sensitive areas, providing a safer and more controlled environment on the Wiiisdom Cloud Platform.
Changing the ownership of a pipeline was previously not possible, making it difficult to transfer responsibilities.
To address this, we implemented a new action that allows a user to give up ownership of a pipeline and assign it to another user. This action includes in-app and email notifications to the new owner, informing them of the change and any necessary updates. This feature is particularly useful when people are changing companies, going on long leave, or transitioning to different roles.
This enhancement improves collaboration, ensures continuity, and simplifies the management of pipelines.
Verifying that a report has not changed between tenants can be time-consuming, tedious, and error-prone when done manually.
To address this, we implemented a new step called Cross Environment Regression Testing, which allows automatic selection and comparison of reports between source and target tenants.
This enhancement streamlines the testing process, ensuring consistency and accuracy, and saves time by automating report mapping and comparison.
Deploying content between Power BI tenants manually was time-consuming and prone to errors.
To address this, we added a new step called "Deploy Content (Cross Environment)" under the "Deployment" section, which allows selecting a target context and workspace. This step includes options to overwrite existing reports and deploy all content of the workspace dynamically. Additionally, a tree structure is provided to select the reports to deploy.
Please note that contrary to the already-existing deploy content step, this step can be used with a Pro license and does not require to attach a capacity to your workspace.
This enhancement streamlines the deployment process, ensures consistency, and saves time by automating the promotion of reports and datasets.
Waiting for a workbook to open can be time-consuming. We added a feature to measure and simulate the workbook opening time. To do so, simply configure your step in such a manner:
This way, your pipeline will verify that the Superstore workbook does not take above 12 seconds to open any views. And if so, we will be able to alert you.
The details of the execution will be shown like so:
Promoting workbooks and data sources to different Tableau sites manually is time-consuming. With the addition of preview sites, these promotions may become more frequent, further increasing the time consumption.
To address this, we implemented a new step called "Promote content (Cross Environment)" in the Promotion category, which allows efficient promotion of Tableau workbooks and data sources to different Tableau sites. We also allow you to change the destination and the name of the object in the target environment.
This enhancement simplifies content management, ensures consistency, and saves time by automating the promotion process. Additionally, this feature is particularly beneficial in a GxP context, as it supports the use of Tableau Preview sites, ensuring compliance and reliability in regulated environments.
▪ Guiding users to create context when shared pipeline results in a 404 page
▪ Improved the error message when using DAX Mode to facilitate debugging
▪ Notify users when a PAT is about to expire
▪ Reduced the amount of user information included in requests when changing ownership or sharing pipelines
▪ Updated Quarkus to 3.20
▪ Generating the site tree cache may cause the pipeline service to crash (Impact: High)
Description: Creating a pipeline simultaneously via the API and the Designer can render the application unusable.
ID: WOFT-2863
▪ Unable to run a pipeline containing a lot of data or a lot of steps (40+) (Impact: High)
Description: Pipelines using a lot of data or more than 40+ steps were not runnable.
ID: WOFT-2770
▪ Cannot create a pipeline with dataset steps in simplement mode and filter with IN/NOT IN operator (Impact: Medium)
Description: When you try to create a Pipeline with dataset steps in simple mode, if you set up a filter where the operator is IN or NOT IN, the application displays a “Internal server error” on save.
ID: WIIIS-1974
▪ Open Report and Simulation journey timings are overestimated (Impact: Medium)
Description: When running an open report step or Simulation journey step, opening and valuation times can be overestimated by factor 2, leading to a FAIL status when you validate opening time.
ID: WIIIS-1959
▪ Simulation journey step may end due to memory issue (Impact: Medium)
Description: Sometime the Simulation Journey step ends with FAILED status without any other error message in the logs due to an issue in internal resource management.
ID: WIIIS-1958
▪ Error trying to run a Step that contains a DAX query with ORDER BY (Impact: Medium)
Description: Running a PowerBI Pipeline Step configured in DAX mode fails when the DAX query contains an “ORDER BY” clause.
ID: WIIIS-1919
▪ Browsing substeps on simulation journey report is not working (Impact: Medium)
Description: When you have a Simulation Journey step with multiple substeps, in the execution report, the browser on the top bar does not properly swaps the images for the different substeps. You can still browse the substep with a pagination feature at the bottom of the report.
ID: WIIIS-1893
▪ Cannot display a report that failed to open on the first page (Impact: Medium)
Description: If your Open Report pipeline ends up in error due to the first page or report unable to be rendered, WCP won’t show the screenshot of the error.
ID: WIIIS-1887
▪ In some cases the underlying PBI dployment pipeline may not release the target workspace (Impact: Medium)
Description: In some case where Power BI prevents us from unassigning the source workspace, we did not unassign the target workspace nor did we remove the pipeline. This prevented us from executing the WCP pipeline later.
ID: WIIIS-1886
▪ When table descriptions are set, we use them instead of name (Impact: Medium)
Description: When table has a description it is used as name in WCP interface, which forces you to use the DAX mode as a workarround to reference the table when decription is too long.
ID: WIIIS-1877
▪ Newly created PAT is not displayed in the PAT list if the "OK" button of the modal is not fired (Impact: Low)
Description: Newly created PATs were not displayed if the modal is not closed using the “Ok” button.
ID: WOFT-2737
▪ When clicking on Open Report "see details", modal is empty (Impact: Low)
Description: When one report failed to open in Open Report step, in the execution report you could not see the details of all the reports listed after this failed report.
ID: WOFT-2706
▪ Unable to allow an URL containing special characters (Impact: Low)
Description: Encoding issue when passing data from the front end to the back end. Special characters were not properly encoded, which caused the full URL not to be received on the back end, resulting in incorrect validation.
ID: WOFT-2701
▪ Cannot fully remove an execution when there is a Duplicated Row step (Impact: Low)
Description: If a pipeline contains a duplicated row step, when you delete an execution, it is not fully deleted, hence some artifact may stay on storage even if now totally not accessible.
ID: WIIIS-1967
▪ User fetching returns too much data (Impact: Low)
Description: When listing users in share and change owner wizard, we expose too many data about the user.
ID: WIIIS-1900
▪ Regarding scanner setup or update: Unable to save changes after refreshing the project tree. (Impact: Low)
Description: If you start configuring your scanner then refresh the tree, all the changes you made afterward were not taken into account.
ID: WIIIS-1881
▪ When dragging a substep in simulation journey, it is possible to shuffle all substeps (Impact: Low)
Description: In some cases the drag and drop of substeps in simulate journey step shuffles the steps.
ID: WIIIS-1878
▪ We do not allow to select a a table that has more than 80 chars in Semantic Model validation steps (Impact: Low)
Description: If one of the column or one of the tables that you selected in Dataset Statistics, Row Count, Dataset Values steps has more than 80 chars we prevented user to save the pipeline. Limit has been increased to 255 chars. It affects both Power BI and Tableau steps. Duplicated Row steps is not affected.
ID: WIIIS-1868
▪ We save a second certification handle when the visual is updated (Impact: Low)
Description: PowerBI certification audit endpoint shows two certification handle if a report was certified after the visual has changed (example resized)
ID: WIIIS-1861
▪ We can trigger without any error a pipeline that has no context (Impact: Low)
Description: If you delete the context your pipeline was relying on, you can start the pipeline but it is stuck in running mode afterward.
ID: WIIIS-1760
▪ User list page does not display the right page number after a user creation or deletion (Impact: Low)
Description: When you create or add a user and you are on another page than the first one, once the creation or deletion process has ended, the pagination number keeps the same but only first page is displayed.
ID: WIIIS-1483
▪ Back to pipelines link is not properly styled and consistent with other links in the application (Impact: Low)
Description: When you are editing a pipeline, the “back to pipelines” link was badly styled and does not seem clickable.
ID: WIIIS-1274
