The 2024.3 release adds support for more Flow integrations, improvements to the TableView, Tab control and Filter components, and adds the Spinner control to Form Schemas.
Flow integration
Publish dimension
You can now define Flows to run after a dimension has been published. Going forward, prefer using Flow instead of Dataflow for running custom business logic after a dimension has been published or published to. Dataflow is still supported, but will be removed in the future.
Work Process Version Deployment
You can now define Flows to run after a Work Process Version has been deployed, opened, closed, and before delete. This is now the preferred way of running custom business logic when a Work Process Version changes state. Dataflow is still supported, but will removed in the future.
Package Deployment
Like with Work Process Version and Dimensions, you can now run Flows after a Package has been deployed or upgraded. Prefer using Flows instead of Dataflows, as Dataflows will be deprecated in the future.
Workbook enhancements and new features
Tab control – API for changing active tabs
You can now programmatically change the active tab of Tab Control components so users can be directed to relevant content based on actions or state in the Workbook.
<Function>
this.controls.myTabControl.activateTab('Customers')
</Function>Filter – fixed issue with Search filter
We’ve fixed an issue with the Search filter that caused an error if the “Load Data” action was not run before it was used.
Forms – Added Spinner control
Developers can now display Spinners in Forms to indicate long running processes, for example while running Flows directly from Form components.
TableView – multiple enhancements
- The Selection column can now be configured to have 3 visibility options
- Never
- On hover – Checkboxes are visible when the user hovers a row
- Always (New) – Checkboxes are always visible
- Wrap filters to new row. If you have a large number of filters, filters will now wrap to a new row in the table header instead of breaking out of the control bounds
- Conditionally enable context menu items. Developers can now specify conditions for whether custom context menu items are enabled or not.
Workbook Page – show and hide
You can now show and hide Workbook pages conditionally using one of the following methods:
- Is Hidden Expression. Use the new Is Hidden Expression (C#) on the Workbook Page to perform a server-side evaluation of whether the page is default hidden or not.
- Show and Hide page actions. Execute the new Show and Hide actions in the Action Tree to dynamically show and hide pages.
- JavaScript API for hiding and showing pages. Use the JavaScript API in Action instructions of Forms to dynamically show and hide pages.
Access Control and Permissions
Support for membership of more than 200 Microsoft Entra groups
We now support that users can be member of more than 200 Microsoft Entra user groups.
That’s all, folks!