• Charts
• Dashboard
• Ad-hoc analysis
• Dashboard Editor
• Studio
• Data models
• Configuration
• Security
  • Rolification
  • Authorization Groups & Authorizations
• Export
• DigDash REST API
• Installation

New features and bug fixes in 2026 R1 have resulted in changes to behaviour that may have an impact. We therefore recommend that you consult the list of behavioural changes below.

Charts

Tooltips

Following the new implementation of tooltips for charts, tooltips:

• may extend beyond the object’s container (portlet);
• follow the movement of the mouse cursor when hovering over an element.
   

Column charts

The Group information on the grouping axis option has been removed.

When using a line chart and a grouping, the line is no longer positioned on the first column of the grouping but in the middle of the grouping.

 

Cross table

Row headers are now treated as headers.
The following options have been revised accordingly:

• ‘Line break on header’ has been replaced by ‘Line break on header cells’.
• ‘Line break on other rows’ has been replaced by ‘Line break on content cells’.

Text in vertical headers is now always aligned at the top of the cell, regardless of the number of rows displayed.
 

Tree tables

The digdash_2024 theme now features a colour gradient for the different sublevels of vertically displayed tree tables (the further down the sublevels you go, the darker the grey becomes).

If you wish to revert to the previous display without the colour gradient (white background), edit the digdash_2024 theme via the Flow editor and set the `background-color` value to #FFFFFF for all rules from ` tr.rowlvl1 ` to `tr.rowlvl5 `, as shown below.

tr.rowlvl1 td:not(.tdvHeader), td.collvl1, td.tdhHeader.collvl0
{
  background-color: #F4F4F4;
}

tr.rowlvl2 td:not(.tdvHeader), td.collvl2, td.tdhHeader.collvl1
{
  background-color: #F0F0F0;
}

tr.rowlvl3 td:not(.tdvHeader), td.collvl3, td.tdhHeader.collvl2
{
  background-color: #E2E2E2;
}

tr.rowlvl4 td:not(.tdvHeader), td.collvl4, td.tdhHeader.collvl3
{
  background-color: #DDDDDD;
}

tr.rowlvl5 td:not(.tdvHeader), td.collvl5, td.tdhHeader.collvl4
{
  background-color: #DCDCDC;
}

tr.rowlvl1 td:not(.tdvHeader), td.collvl1, td.tdhHeader.collvl0
{
  background-color: #FFFFFF;
}

tr.rowlvl2 td:not(.tdvHeader), td.collvl2, td.tdhHeader.collvl1
{
  background-color: #FFFFFF;
}

tr.rowlvl3 td:not(.tdvHeader), td.collvl3, td.tdhHeader.collvl2
{
  background-color: #FFFFFF;
}

tr.rowlvl4 td:not(.tdvHeader), td.collvl4, td.tdhHeader.collvl3
{
  background-color: #FFFFFF;
}

tr.rowlvl5 td:not(.tdvHeader), td.collvl5, td.tdhHeader.collvl4
{
  background-color: #FFFFFF;
}

Tiles

The background colour of the areas is now inherited from the default theme.
 

Gauges

Gauges are now visible without a theme.

PDF builder/PPT Builder

The size and position of elements are no longer relative values but absolute values.
 

Treemap, Maps, Timeline

Labels for Treemap, Maps and Timeline charts are now grey for the digdash_2019 and digdash_2024 themes.
To force the labels to be displayed in black, edit the theme and add the following CSS:

Font

The Open Sans font is used by default for labels and tooltips on all charts.

Two new variables have been added for bold or semi-bold text in charts. If you wish to change the font used, you will therefore need to amend these variables as well:

--dd-font-family-fontFamilyBold
--dd-font-family-fontFamilySemibold

Theme

The ‘Border collapse like with sticky header’ theme has been replaced by the‘Table border-collapse like with sticky header’ theme for displaying single borders on tables.

Some CSS styles may be ignored due to a lack of specificity.
We now recommend using variables rather than standard CSS rules (best practice).

Top/Bottom values

If you update DigDash from a version 2025 R2 prior to patch P12, some of your existing charts configured with the “Top/Bottom values” option in “Global” mode will automatically switch to “Local” mode. Please check your charts after the update to restore “Global” mode if necessary.

Dashboard

Object header

In the case of an object (portlet) with the “Show window header” option ticked and the “Show window border” option unticked, thedigdash_2024theme would always display a transparent header background, regardless of the value of the--background-color-portlet variable.
The header background is now defined by the--background-color-portlet variable (which defaults to white), as was already the case with thedigdash_2019 theme.
 

Variables

The display of variable titles has been brought into line with that of other object types.
 

Description

Descriptions added to a dashboard object no longer have the title “Description” by default.
You can, however, add a title if you wish.
 

Flow loading

For optimisation purposes, the way flows (charts) are loaded has been modified depending on the entry point:

• Dashboard (viewing): Only the flows on the page being viewed are loaded. When navigating, the system retrieves only the new flows that are required. If a flow has already been loaded on a previous page, it is reused without making a new call to the server.
• Embedded dashboard: Only the flows specifically declared in the page’s HTML or JavaScript tags are loaded.
• Theme Editor: No flows are loaded. A view dashboard embedded in an iframe is created for the preview. This instance loads the flows present on the current page.
   

Area selection mode

A new option allows you to show or hide the area selection mode options menu icon in chart windows. The icon is hidden by default.
 

Scrolling & retractable objects

The presence of a retractable object would prevent page scrolling depending on its orientation:

• horizontal scrolling was not possible if a retractable object was positioned on the left or right.
• Vertical scrolling was not possible when a retractable object was positioned at the top or bottom.

These restrictions have been removed and scrolling is now smooth in all cases.
 

Web integration and HTML reports

To ensure they display correctly in embedded mode, icons in HTML report-type charts must be added using keywords in the following format:

${vectoricon.image_name.svg}         //public vector icon added via Studio
${vectoricon.roleId/image_name.svg}  //role-based vector icon added via Studio
${icon.image_name.png}               //public icon added via the Dashboard Editor
${icon.roleId/image_name.png}       //role-based icon added via the Dashboard Editor

Dashboard entry point

The index.html file is no longer the dashboard entry point; any changes made to this file must be reflected in the index.jsp file.

Ad-hoc analysis

Filters added via ad hoc analysis

Filters added via ad hoc analysis are now public. Consequently,

• they are visible in the ‘Filtered Items’ object
• they are applied to the other charts on the page

Furthermore, when applying the view with the saved filters, all filters in the table are reset.

💡Case of views saved in a version prior to version 2026 R1

If you save an old view, it will adopt this new behaviour (public filters and dashboard reset). The view’s filters are added to the dashboard and propagate to other pages. To prevent this propagation and revert to the previous behaviour, simply isolate the page containing the ad hoc analysis by setting its navigation type to “Private”.

Filters from Studio

Any dimension defined as non-navigable in Studio could not be filtered, nor could its filter be modified or deleted in the ad hoc analysis.
This is no longer the case.
However, the previous behaviour can be restored in the advanced features via the option:
canEditInitialFilters: false

Non-navigable filters added via Studio were not only uneditable in the ad hoc analysis, but were also not saved in the view. The view contained only filters added via ad-hoc analysis or the dashboard. Filters originating from Studio were ignored during saving but were applied when the view was loaded. Consequently, Studio filters could be dynamic: if they changed, so did the view.
From now on, as described in the ‘Filters’ section above, non-navigable Studio filters can be edited in ad hoc analysis. They are therefore also saved in the view and are no longer dynamic. If the original filter changes in Studio, the saved view will not change.

Dashboard Editor

Advanced editing of a chart

To edit a chart using advanced editing features, you must have the ‘Flows > Save Flows’ authorisation for a role, in addition to the ‘Studio > Access to Studio’ authorisation.
 

Chart options

By default, the iconfor accessing the area selection mode options is no longer displayed on charts in the Dashboard.
You can enable it by ticking the ‘Show chart options (selection mode...)’ option in the chart properties.
 

Themes & JavaScript Files

It is now possible to restrict a theme or JavaScript file to a specific role. See the section Rolification for further details.
 

Dashboard Properties

The ‘Magnetic Grid Size’ and ‘Enable Object Placement Hints’ options have been removed.

It is now possible to define dashboard properties either globally or on a role-specific basis. See the section Role-Based Configuration for further details.

Images

The process for adding images in the Dashboard Editor has changed.
The concept of ‘scope’ has been replaced by that of ‘role’, and it is no longer possible to associate an image with the current user. See the section Rolification for further details.

Studio

PDF/PPT Document Builder

The ‘Keep ratio’ tick box, which allowed the proportions of an element to be preserved when it was resized, has been replaced by the .
 

User session

If Studio is open both in its own tab and from within the Table Editor (advanced editing of a chart), the session is now shared. If the user logs out in one window, they are logged out in all windows. A warning message has been added.
 

Vector icons

It is now possible to restrict a vector icon to a specific role. See the section Rolification for further details.

Data models

Quotas

The user must have the Admin > Manage Quotas on Data Models authorization in order to set specific cube quotas for data models.
 

Configured connection

Following changes to user settings, the user can view only the common user settings (role “None”) or the user settings for the roles they hold in the list of configured connections.
 

Live Security functions

Live Security functions created using the wizard can now be restricted to a specific role.
 

Calculated Measures

The log('') function replaces the advanced syntax Packages.com.digdash.utils.MessageStack.getInstance().addText("") for inserting a debug trace into the logs.

Configuration

Users

The Username (cn) field has been removed.
 

User/role name

The following characters are now prohibited in a user or role name when creating or editing it:

/ \ : * ? " < > | ` % +

User profiles

Authorizations relating to user profiles have changed. See the section Authorization Groups and Authorizations for further details.
 

User settings

Authorizations relating to user settings have changed. See the section Authorization groups and authorizations for further details.
 

Non-incremental backup

Backup/restore in non-incremental mode is now possible by role.
When restoring a complete role backed up in non-incremental mode, all files within the role are overwritten.
An information message has been added for backups in non-incremental mode.
 

Backing up/restoring system files

It is not possible to back up or restore the system filesapikeys.csv,quotarepository.xml,ldapsettings.xml,serversettings.xml and system.xml when the ServerSettingsPath parameter is set outside the appdata/Enterprise Server directory.

Backing up/restoring map files

Rolification control for map files is taken into account during backup and restore.
The files remain in the public directory (appdata/Enterprise Server/ddenterpriseapi/config/web/public/maps/mapId/....) but you must now have the following combination of authorizations to perform the backup/restore:

• Studio > Access the Map Manager and Elements > Manage role elementsfor a role-restricted map.
• Studio > Access to the Map Manager and Elements > Manage common elements for a shared map.

Security

Rolification

The Rolification  for elements has been revised and extended.

Rolification rules

The following rules now apply to all role-assigned elements:

• An element common to all roles (“None”) cannot be restricted to a specific role.
• An element restricted to a role cannot be reassigned to another role.
• A restricted element may become common to all roles (“None”).

Authorizations

Managing elements requires the following authorizations:

• Elements > Manage role elements to manage elements restricted to a role
• Elements > Manage shared elements to manage elements shared by all roles

Backup & Restore

In the backup/restore interface, only those elements for which the user has the necessary rights (based on their authorizations and roles) are available.

New rolified elements

Elements created prior to version 2026R1 are considered common to all roles.

Theme & JavaScript Files

Storage and authorizations

Themes or JavaScript files may be:

• shared across all roles (the “None” role):

  Type	Storage directory	Required authorizations
  Theme	appdata/Enterprise Server/ddenterpriseapi/config/web/public	Dashboard > Manage Themes andElements > Manage Common Elements
  JavaScript file	appdata/Enterprise Server/ddenterpriseapi/config/web/session	Dashboard > Manage JavaScript Files andElements > Manage Common Elements

• Restricted to a role:

  Type	Storage directory	Required authorizations
  Theme	appdata/Enterprise Server/ddenterpriseapi/config/web/{roleId}	Dashboard > Manage Themes andElements > Manage Role Elements
  JavaScript file	appdata/Enterprise Server/ddenterpriseapi/config/web/{roleId}	Dashboard > Manage JavaScript Files andElements > Manage Role Elements

Migration

The Dashboard > Manage Themes and Dashboard >Manage JavaScript Files authorizationsare assigned by default to users who already have the Dashboard > Dashboard Customisation authorization at the time of migration.
They are also added by default to the Supervisor and Dashboard Designer authorisation groups.

The ‘Elements > Manage Role Elements’ authorisation is added by default to the ‘Dashboard Designer’ authorisation group.
The‘Elements > Manage Shared Elements’ authorisation must be added to manage shared themes and JavaScript files.
 

Dashboard properties

Dashboard properties can be defined globally or on a role-specific basis.

Storage and authorizations

Migration

The ‘Elements > Manage Role Elements’ authorisation is added by default to the ‘Dashboard Designer’ authorisation group.
The‘Elements > Manage Common Elements’ authorisation must be added to edit common properties.
 

Images

The process for adding images in the Dashboard Editor has changed.
The concept of ‘scope’ has been replaced by that of ‘role’, and it is no longer possible to associate an image with the current user.

In a role context (selecting a background or icon for a role, page or object), the user will only be able to see shared images or images for the current role in the list of available images.
They will be able to view and manage shared images as well as those for all the roles they hold in Images Manager.
 

Storage and authorizations

Vector icons

User settings

When the server starts up, a migration is carried out to move user settings from the usersettings.xml file to the userparamrepository.xml file .

Storage and authorizations

Authorization Groups & Authorizations

Renamed authorizations

The following authorizations have been renamed:

Authorization groups

System Administrator

The following authorizations have been added to the System Administrator authorization group:

• Admin > Manage user settings
• Admin > Edit a user’s protected settings
• Admin > Manage quotas on data models
• Admin > Assign a profile to a user
   

Role Administrator

The following authorizations have been added to the Role Administrator authorization group:

• Admin > Edit a user’s protected settings
• Admin > Manage user settings
• Items > Manage role items
• Studio > Access to the device manager
• Studio > Access to the format manager
• Studio > Access to the map manager
• Studio > Access to the database connection manager
• Studio > Access to the predefined functions manager
• Studio > Access to the hierarchy Manager
• Studio > Access to the icon manager
• Studio > Access to the colour palette manager
• Studio > Access to the schedule manager
• Studio > Access to the styles manager
• Studio > Access to the translation manager
• Studio > Edit a data source for a role
• Dashboard > Edit dashboard for a role
• Dashboard > Manage JavaScript files
• Dashboard > Manage themes
• Dashboard > Customising the dashboard
• Dashboard > Create a form
   

Dashboard Designer

The following authorizations have been added to the Dashboard Designer authorization group:

• Elements > Manage role elements
• Studio > Edit a database data source
• Studio > Edit a data catalog data source
• Studio > Edit a file data source
• Studio > Edit an IO data source
• Studio > Edit a join data source
• Studio > Edit a report data source
• Studio > Edit a column transformer data source
• Studio > Edit a data source of the data transformer type
• Studio > Edit a union data source
• Studio > Edit a data source for a role
• Dashboard > Manage JavaScript files
• Dashboard > Manage themes
   

End User for Self-service BI

The following authorizations have been added to the End User for Self-service BI authorization group:

• Content > List documents
• Content > List document servers
• Content > Submit a document
• Content > Delete or update a document
   

User profiles

Authorizations relating to user profiles have changed:

• The authorisation in previous versions, Admin > Manage user profiles, allows the user to create, edit and delete a user profile
• The new authorization Admin > Assign a profile to a user allows the user to assign user profiles (of which they have access) to a user.
  It is assigned by default to users who already have the Admin > Edit a user’s attributes authorization during migration.
  It is also added by default to the ‘Supervisor’ and ‘System Administrator’ authorization groups.

User settings

Authorizations relating to user settings have changed:

• The authorisations that existed in previous versions Admin > Edit a user’s settings and Admin > Edit a user’s protected settings – allow the user to change the value of a user setting or, respectively, the value of a protected setting.
• The new authorization ‘Admin > Manage user settings’ allows the user to create, edit and delete a user setting.
  It is assigned by default to users who already have the authorizations‘Admin > Edit a user’s settings’ and ‘Admin > Manage users’ during migration.
  It is also added by default to the Supervisor and System Administrator authorization groups.

Export

Tables and sort icon

The sort icon (arrow) was not displayed or was displayed incorrectly when exporting a table.
For PPT and Excel exports, an arrow symbol in the same colour as the text now indicates the sort order.
For PDF exports: the sort icon changes colour and appears to the right of the header text.

DigDash REST API

Profile

The “dd_profil_” profile prefix is no longer displayed.

Previously, in the API, when calling `getProfiles`, all profiles were visible if the user had the‘Admin > Manage user profiles’ authorization. Now, only those profiles for which the user has the necessary authorizations are returned. In other words, only those profiles for which the user holds all the authorizations and roles associated with the profile are visible.
 

User & Profile

When retrieving users and profiles, the API no longer returns the full list of authorisations in addition to the authorisation groups.

Changes to the structure of the groupAcls field

The groupAcls field was previously an array of complex objects. Each object contained an identifier (id) and a sub-array of authorisations (aclList).
The structure has been simplified. The groupAcls field is now a simple array of strings (e.g. ["groupAcls", "groupAcls"]). The intermediate id and aclList elements have been removed so that values are stored directly at the root of the array.

Before 2026 R1	Since 2026 R1

Roles

It is now possible to specify role authorizations (RWX or authorization groups) during a POST (add) or PUT (replace) operation on a user or profile.

Installation

Tomcat 9 is no longer supported. Only Tomcat 10 is supported.