Skip to main content

Hello everyone!

In this release of the Thinkwise Platform, we have significantly improved the configuration of action bars for the Universal GUI. You now have more control over the placement of action bars on a screen and can manage their content and appearance more flexibly. In addition, the new UI Styling has been applied to the new action bars.

We have also added a number of other new user interface features for the Universal GUI, such as collapsible sections for forms, a relative setting for the form column width, and expanding settings for grids.

Cubes are now more user-friendly to set up as well. We have redesigned the cube screen and added support for editable pivot grids and calculated cube fields in the Universal GUI.

The most significant new feature in IAM is the ability to schedule the clean-up of applications, branches, and models. You can set up a process to help you keep your IAM environment tidy by automatically removing applications, branches, and models that are no longer in use.

With this release, we also introduce the first official version of the Windows GUI (3-tier) via Indicium, making Indicium Basic end-of-life. This year (2025) is the last year the 2-tier architecture is supported. Note that the Windows GUI (3-tier) is a backup plan if moving to the Universal GUI directly proves problematic. It is only available for those participating in the early-adopter program. The 3-tier architecture is much more secure and stricter regarding the quality of your model, so to prepare for the transition to the Universal GUI or to the Windows GUI (3-tier), we recommend fixing all findings in validations and smoke tests.

This release contains 25 Community ideas representing a record of 588 votes. The most popular ideas were:

This post highlights the key features of the release. For detailed release notes, visit the Thinkwise Documentation.

Contents

 

User interface - More control over action bar placement in Universal GUI

change Universal GUI

In this release, we have significantly improved the configuration of screen types for the Universal GUI. Some of the most important changes are in the configuration of Detail groups:

  • The setting Detail groups has been renamed to Screen areas. Fallback groups have also been renamed, from Fallback group to Fallback area.
  • You can now assign a screen area not only to details but also to task and report tiles, and to task, report, prefilter, and cube view bars. Assigning screen areas to tiles and bars allows you to place buttons for table tasks, table reports, prefilters, and cube views in different locations on a screen. You can reuse a screen area multiple times within a screen type, allowing tiles and buttons to be available more than once per screen.

As a result, you have more flexibility in positioning bars within a screen type. Previously, the Universal GUI would automatically place action bars in screens. Now, two types of action bars are available, and you can define their content and appearance in more detail:

  • The Action bar follows the default configuration defined for a branch. Changes to this default configuration affect all screens with Action bars. At the screen type level, you can include and exclude actions.
  • In a Custom action bar, you can include or exclude actions, and change their order, default display type, screen area, and fallback settings. You can use screen areas to assign table tasks, table reports, prefilters, or cube views to a Custom action bar.
Custom action bar configuration

 

User interface - New features for the Universal GUI

new Universal GUI

In addition to the improvements to the action bars, we have added some other new user interface features for the Universal GUI:

  • Collapsible sections for forms. By default, all sections are expanded, showing all columns inside them.
  • A Form column width factor setting to adjust relative form column width sizes.
  • The Max. form-col space shows the form column space as a percentage of a form field, report parameter, or task parameter.
  • Multi-row selection for grids.
  • Hierarchical grouping of resources in a Scheduler.
  • A maximum size limit for modal documents.

 

Cube enhancements

Community idea new change

We have enhanced a number of cube-related screens to improve clarity and usability. These changes will help you configure your cube views more efficiently. Some of the most important changes are:

  • In the menu group User interface, the menu item for cubes is now called Cubes instead of Business intelligence.
  • Instead of a single tab for Cube fields, there are now two separate tabs for Dimensions and Values.
  • The new Cube set-up panel allows you to configure the cube view fields visually, similar to how you would create a cube view in your application.
  • Settings specific to the cube view type are now available in vertical detail tabs: Pivot settings, Chart settings, Filter and Sort.

For the Universal GUI, we have added support for editable pivot grids. For the Windows GUI, the extender default_editable_cube remains available but is no longer necessary if you are transitioning to the Universal GUI.

Another new feature for the Universal GUI is the ability to create calculated cube fields of the type Value. You can set the Aggregation type to SQL expression and enter an expression. For the Windows GUI, the checkbox Calculated field has been replaced with Aggregation type Formula (deprecated). If you are transitioning from the Windows GUI to the Universal GUI, you can add both settings to your cube view. Aggregation type will be ignored by the Windows GUI, and Aggregation type Formula (deprecated) will be ignored by the Universal GUI.

The new cube setup panel

 

Translations - Generate alternative translations for objects

Community idea new Universal GUI Windows GUI (3-tier)

In the Thinkwise Community, a highly requested feature was the ability to create alternative translations for objects. This feature is now available, allowing you to generate an alternative translation label for table (variant) columns, task (variant) parameters, and report (variant) parameters. It enables you to keep generic column names while customizing translations in your applications based on context or specific use cases.

Add an alternative translation

 

Some other new features

  • For models, you can now limit branch access for users to prevent accidental changes to a branch. This is especially useful for the MAIN branch, where changes are typically not made directly but instead added through merging.
  • A new file storage type is available: SFTP. It can be used to access files on an SSH FTP server, which is useful for secure file transfers.
  • For variants, we have added a new screen that shows an exact overview of how the variant differs from the default. In addition, variants are now also displayed in the Usage tabs, indicating that an object is used in a variant.
  • For Oracle, we have added:
    • Support for sequences in models
    • Unit tests
    • Smoke tests
  • We enhanced validations by adding tasks that affect all messages for a validation at once and improving descriptions. We also added several new validations.

 

Questions or suggestions?

Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Be the first to reply!