Changes in behaviour

----

(% class="wikigeneratedid" id="HModificationsdecomportementdansla2023R1" %)

{{id name="Deploiement_patch"/}}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{{id name="tooltip"/}}**

11

12

(% class="box infomessage" %)

13

(((

14

**ℹ** OpenStreetMap charts are not affected by this change.

15

)))

16

17

Following the new implementation of tooltips for charts, tooltips:

18

19

* may extend beyond the object’s container (portlet);

20

* 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.

26

27

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.

28

[[image:1779875924335-821.png||height="224" width="458"]]

29

30

31

**{{glossaryReference glossaryId="Glossary" entryId="Tableau croisé"}}Cross table{{/glossaryReference}}**

32

33

Row headers are now treated as headers.

34

The following options have been revised accordingly:

35

36

* //‘Line break on header//’ has been replaced by //**‘Line break on header cells**//’.

37

* //‘Line break on other rows//’ has been replaced by //**‘Line break on content cells**//’.

38

39

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).

45

46

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

▶ Display code Grey gradient

52

</summary>

53

54

tr.rowlvl1 td:not(.tdvHeader), td.collvl1, td.tdhHeader.collvl0

55

{

56

background-color: #F4F4F4;

57

}

58

59

tr.rowlvl2 td:not(.tdvHeader), td.collvl2, td.tdhHeader.collvl1

60

{

61

background-color: #F0F0F0;

62

}

63

64

tr.rowlvl3 td:not(.tdvHeader), td.collvl3, td.tdhHeader.collvl2

65

{

66

background-color: #E2E2E2;

67

}

68

69

tr.rowlvl4 td:not(.tdvHeader), td.collvl4, td.tdhHeader.collvl3

70

{

71

background-color: #DDDDDD;

72

}

73

74

tr.rowlvl5 td:not(.tdvHeader), td.collvl5, td.tdhHeader.collvl4

75

{

76

background-color: #DCDCDC;

}</pre>

</details>

▶ See code White background

83

</summary>

84

85

tr.rowlvl1 td:not(.tdvHeader), td.collvl1, td.tdhHeader.collvl0

86

{

87

background-color: #FFFFFF;

88

}

89

90

tr.rowlvl2 td:not(.tdvHeader), td.collvl2, td.tdhHeader.collvl1

91

{

92

background-color: #FFFFFF;

93

}

94

95

tr.rowlvl3 td:not(.tdvHeader), td.collvl3, td.tdhHeader.collvl2

96

{

97

background-color: #FFFFFF;

98

}

99

100

tr.rowlvl4 td:not(.tdvHeader), td.collvl4, td.tdhHeader.collvl3

101

{

102

background-color: #FFFFFF;

103

}

104

105

tr.rowlvl5 td:not(.tdvHeader), td.collvl5, td.tdhHeader.collvl4

106

{

107

background-color: #FFFFFF;

}</pre>

</details>

**Tiles**

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

**Gauges**

Gauges are now visible without a theme.

121

122

**{{glossaryReference glossaryId="Glossary" entryId="Fabrique PDF"}}PDF builder{{/glossaryReference}}/{{glossaryReference glossaryId="Glossary" entryId="Fabrique PPT"}}PPT Builder{{/glossaryReference}}**

123

124

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

125

126

127

**Treemap, Maps, Timeline**

128

129

Labels for Treemap, Maps and Timeline charts are now grey for the //digdash_2019// and //digdash_2024// themes.

130

To force the labels to be displayed in black, edit the theme and add the following CSS:

.lbtxt, .treemapVal

{

fill : black;

}

**Font**

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

143

144

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:

145

146

{{{--dd-font-family-fontFamilyBold

147

--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.

154

155

Some CSS styles may be ignored due to a lack of specificity.

156

We now recommend using variables rather than standard CSS rules (best practice).

157

158

159

**Top/Bottom values**

160

161

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, the//digdash_2024//theme would always display a transparent header background, regardless of the value of the//~-~-background-color-portlet// variable.

168

The header background is now defined by the**//~-~-background-color-portlet //**variable (which defaults to white), as was already the case with the//digdash_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.

179

You can, however, add a title if you wish.

180

181

182

**{{glossaryReference glossaryId="Glossary" entryId="Flux"}}Flow{{/glossaryReference}} loading**

183

184

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

185

186

* 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.

187

* Embedded dashboard: Only the flows specifically declared in the page’s HTML or JavaScript tags are loaded.

188

* 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.

189

190

191

**Area selection mode**

192

193

A new option allows you to show or hide the area selection mode options menu icon [[image:1779865402009-790.png||height="24" width="28"]]in chart windows. The icon is hidden by default.

194

195

196

**Scrolling & retractable objects**

197

198

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

199

200

* horizontal scrolling was not possible if a retractable object was positioned on the left or right.

201

* Vertical scrolling was not possible when a retractable object was positioned at the top or bottom.

202

203

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

204

205

206

**Web integration and HTML reports**

207

208

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

209

210

{{{${vectoricon.image_name.svg} //public vector icon added via Studio

211

${vectoricon.roleId/image_name.svg} //role-based vector icon added via Studio

212

${icon.image_name.png} //public icon added via the Dashboard Editor

213

${icon.roleId/image_name.png} //role-based icon added via the Dashboard Editor

}}}

**Dashboard entry point**

218

219

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**

224

225

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

226

227

* they are visible in the ‘Filtered Items’ object

228

* they are applied to the other charts on the page

229

230

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

231

232

__💡Case of views saved in a version prior to version 2026 R1__

233

234

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”.

235

236

237

**Filters from Studio**

238

239

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.

240

This is no longer the case.

241

However, the previous behaviour can be restored in the advanced features via the option:

242

//canEditInitialFilters: false//

243

\\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.

244

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.

245

246

= **Dashboard Editor{{id name="éditeur"/}}** =

247

248

**Advanced editing of a chart**

249

250

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 icon[[image:1779097571457-820.png||height="24" width="27"]]for accessing the area selection mode options is no longer displayed on charts in the Dashboard.

256

You can enable it by ticking the **‘Show chart options (selection mode...)’** option in the chart properties.

257

258

259

**Themes & JavaScript Files**

260

261

It is now possible to restrict a theme or JavaScript file to a specific role. See the section [[Rolification>>doc:||anchor="Rolification"]] for further details.

262

263

264

**Dashboard Properties**

265

266

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

267

268

It is now possible to define dashboard properties either globally or on a role-specific basis. See the section [[Role-Based Configuration >>doc:||anchor="Rolification"]]for further details.

**Images**

The process for adding images in the Dashboard Editor has changed.

273

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 >>doc:||anchor="Rolification"]]for further details.

= Studio =

**PDF/PPT Document Builder**

278

279

The **‘Keep ratio**’ tick box, which allowed the proportions of an element to be preserved when it was resized, has been replaced by the [[image:1778493634698-891.png||alt="Cadenas"]].

**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 >>doc:||anchor="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.

296

297

298

**Configured connection**

299

300

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.

301

302

303

**Live Security functions**

304

305

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

306

307

308

**Calculated Measures**

309

310

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:

322

323

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

}}}

**User profiles**

Authorizations relating to user profiles have changed. See the section [[Authorization Groups and Authorizations>>doc:||anchor="acl"]] for further details.

330

331

332

**User settings{{id name="user_param"/}}**

333

334

Authorizations relating to user settings have changed. See the section [[Authorization groups and authorizations>>doc:||anchor="acl"]] for further details.

335

336

337

**Non-incremental backup**

338

339

Backup/restore in non-incremental mode is now possible by role.

340

When restoring a complete role backed up in non-incremental mode, all files within the role are overwritten.

341

An information message has been added for backups in non-incremental mode.

342

343

344

**Backing up/restoring system files**

345

346

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

347

348

349

**Backing up/restoring map files**

350

351

Rolification control for map files is taken into account during backup and restore.

352

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:

353

354

* //Studio > Access the Map Manager// and //Elements > Manage role elements//for a role-restricted map.

355

* //Studio > Access to the Map Manager// and //Elements > Manage common elements// for a shared map.

= Security =

== Rolification{{id name="rolification"/}} ==

360

361

The Rolification for elements has been revised and extended.

362

363

=== **Rolification rules** ===

364

365

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

366

367

* An element common to all roles (“None”) cannot be restricted to a specific role.

368

* An element restricted to a role cannot be reassigned to another role.

369

* A restricted element may become common to all roles (“None”).

370

371

=== **Authorizations** ===

372

373

Managing elements requires the following authorizations:

374

375

* //Elements > Manage role elements// to manage elements restricted to a role

376

* //Elements > Manage shared elements// to manage elements shared by all roles

377

378

=== **Backup & Restore** ===

379

380

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

381

382

=== **New rolified elements** ===

383

384

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

385

386

==== **Theme & JavaScript Files** ====

387

388

**Storage and authorizations**

389

390

Themes or JavaScript files may be:

391

392

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

393

|(% style="background-color:#f2f5f8" %)**Type**|(% style="background-color:#f2f5f8" %)**Storage directory**|(% style="background-color:#f2f5f8" %)**Required authorizations**

394

|**Theme**|//appdata/Enterprise Server/ddenterpriseapi/config/web/public//|//Dashboard > Manage Themes //**and**//Elements > Manage Common Elements//

395

|**JavaScript file**|//appdata/Enterprise Server/ddenterpriseapi/config/web/session//|//Dashboard > Manage JavaScript Files //**and**//Elements > Manage Common Elements//

396

)))

397

398

* Restricted to a role:(((

399

|(% style="background-color:#f2f5f8" %)**Type**|(% style="background-color:#f2f5f8" %)**Storage directory**|(% style="background-color:#f2f5f8" %)**Required authorizations**

400

|**Theme**|//appdata/Enterprise Server/ddenterpriseapi/config/web/{roleId}//|//Dashboard > Manage Themes //**and**//Elements > Manage Role Elements//

401

|**JavaScript file**|//appdata/Enterprise Server/ddenterpriseapi/config/web/{roleId}//|//Dashboard > Manage JavaScript Files //**and**//Elements > Manage Role Elements//

)))

**Migration**

//The Dashboard > Manage Themes and Dashboard >Manage JavaScript Files //authorizations//are //assigned by default to users who already have the //Dashboard > Dashboard Customisation// authorization at the time of migration.

407

They are also added by default to the **Supervisor** and **Dashboard Designer** authorisation groups.

408

409

The //‘Elements > Manage Role Elements’// authorisation is added by default to the **‘Dashboard Designer’** authorisation group.

410

The//‘Elements > Manage Shared Elements’// authorisation must be added to manage shared themes and JavaScript files.

411

412

413

==== **Dashboard properties** ====

414

415

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

416

417

**Storage and authorizations**

418

419

|(% style="background-color:#f2f5f8" %)**Properties...**|(% style="background-color:#f2f5f8; width:530px" %)**Storage directory**|(% style="background-color:#f2f5f8; width:646px" %)**Authorizations required to edit dashboard properties**

420

|Global / common to all roles (role “None”)|(% style="width:530px" %)//appdata/Enterprise Server/ddenterpriseapi/config/dashboardsettings.xml//|(% style="width:646px" %)(((

421

//Elements > Manage common elements//**and**//Dashboard > Dashboard customisation//

422

)))

423

|Restricted to a specific role|(% style="width:530px" %)//appdata/Enterprise Server/ddenterpriseapi/config/roles/roleId/dashboardsettings_roleId.xml//|(% style="width:646px" %)(((

424

//Elements > Manage role elements//**and **//Dashboard > Dashboard customisation//

)))

**Migration**

The //‘Elements > Manage Role Elements’// authorisation is added by default to the **‘Dashboard Designer’** authorisation group.

430

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.

436

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.

437

438

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.

439

They will be able to view and manage shared images as well as those for all the roles they hold in **Images Manager**.

440

441

442

**Storage and authorizations**

443

444

|(% style="background-color:#f2f5f8; width:384px" %)**Image...**|(% style="background-color:#f2f5f8; width:447px" %)**Storage directory**|(% style="background-color:#f2f5f8; width:661px" %)**Authorizations required to add an image**

445

|(% style="width:384px" %)Common to all roles (“None” role)|(% style="width:447px" %)//appdata/Enterprise Server/ddenterpriseapi/config/web/public//|(% style="width:661px" %)(((

446

//Items > Manage common items //and** **//Dashboard > Dashboard customisation//

447

)))

448

|(% style="width:384px" %)Restricted to a role|(% style="width:447px" %)//appdata/Enterprise Server/ddenterpriseapi/config/web/{roleId}//|(% style="width:661px" %)(((

449

//Items > Manage role items //and** **//Dashboard > Dashboard customisation//

450

)))

451

452

==== **Vector icons** ====

453

454

|(% style="background-color:#f2f5f8; width:385px" %)**Vector icon...**|(% style="background-color:#f2f5f8; width:442px" %)**Storage directory**|(% style="background-color:#f2f5f8; width:665px" %)**Authorizations required to add a vector icon**

455

|(% style="width:385px" %)Common to all roles (None)|(% style="width:442px" %)//appdata/Enterprise Server/ddenterpriseapi/config/web/public/vectoricons//|(% style="width:665px" %)(((

456

//Elements > Manage Common Elements //**and**//Studio > Access to the Icon Manager//

457

)))

458

|(% style="width:385px" %)Restricted to a specific role|(% style="width:442px" %)//appdata/Enterprise Server/ddenterpriseapi/config/web/{roleId}/vectoricons//|(% style="width:665px" %)(((

459

//Elements > Manage role elements //**and**//Studio > Access the icon manager//

460

)))

461

462

==== **User settings{{id name="user_param"/}}** ====

463

464

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

465

466

**Storage and authorizations**

467

468

|(% style="background-color:#f2f5f8; width:371px" %)**User settings...**|(% style="background-color:#f2f5f8; width:491px" %)**Storage directory**|(% style="background-color:#f2f5f8; width:694px" %)**Authorizations required to create the user setting**

469

|(% style="width:371px" %)Common to all roles (None)|(% style="width:491px" %)//appdata/Enterprise Server/ddenterpriseapi/config/userparamrepository.xml//|(% style="width:694px" %)(((

470

//Elements > Manage Common Elements//**and**//Admin > Manage User Settings//

471

)))

472

|(% style="width:371px" %)Restricted to a role|(% style="width:491px" %)//appdata/Enterprise Server/ddenterpriseapi/config/roles/roleId/userparamrepository_roleId.xml//|(% style="width:694px" %)(((

473

//Elements > Manage role elements//**and**//Admin > Manage user settings//

474

)))

475

476

== Authorization Groups & Authorizations{{id name="acl"/}} ==

477

478

=== **Renamed authorizations** ===

479

480

The following authorizations have been renamed:

481

482

(% style="width:762px" %)

483

|(% style="background-color:#f2f5f8; width:339px" %)**Old name**|(% style="background-color:#f2f5f8; width:421px" %)**New name**

484

|(% style="width:339px" %)Studio > Manage common items

485

Studio > Manage role items|(% style="width:421px" %)Items > Manage common items

486

Items > Manage role items

487

|(% style="width:339px" %)Wallet > Add a flow

488

Wallet > Add role flow

489

Wallet > Open the flows of a role

490

Wallet > Refresh a flow

491

Wallet > Refresh role flow

492

Wallet > Save the flows of a role|(% style="width:421px" %)Flows > Add a flow

493

Flows > Add role flow

494

Flows > Open the flows of a role

495

Flows > Refresh a flow

496

Flows > Refresh role flow

497

Flows > Save the flows of a role

498

499

=== **Authorization groups** ===

500

501

**System Administrator**

502

503

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

504

505

* Admin > Manage user settings

506

* Admin > Edit a user’s protected settings

507

* Admin > Manage quotas on data models

508

* Admin > Assign a profile to a user

509

510

511

**Role Administrator**

512

513

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

514

515

* Admin > Edit a user’s protected settings

516

* Admin > Manage user settings

517

* Items > Manage role items

518

* Studio > Access to the device manager

519

* Studio > Access to the format manager

520

* Studio > Access to the map manager

521

* Studio > Access to the database connection manager

522

* Studio > Access to the predefined functions manager

523

* Studio > Access to the hierarchy Manager

524

* Studio > Access to the icon manager

525

* Studio > Access to the colour palette manager

526

* Studio > Access to the schedule manager

527

* Studio > Access to the styles manager

528

* Studio > Access to the translation manager

529

* Studio > Edit a data source for a role

530

* Dashboard > Edit dashboard for a role

531

* Dashboard > Manage JavaScript files

532

* Dashboard > Manage themes

533

* Dashboard > Customising the dashboard

534

* Dashboard > Create a form

535

536

537

**Dashboard Designer**

538

539

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

540

541

* Elements > Manage role elements

542

* Studio > Edit a database data source

543

* Studio > Edit a data catalog data source

544

* Studio > Edit a file data source

545

* Studio > Edit an IO data source

546

* Studio > Edit a join data source

547

* Studio > Edit a report data source

548

* Studio > Edit a column transformer data source

549

* Studio > Edit a data source of the data transformer type

550

* Studio > Edit a union data source

551

* Studio > Edit a data source for a role

552

* Dashboard > Manage JavaScript files

553

* Dashboard > Manage themes

554

555

556

**End User for Self-service BI**

557

558

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

559

560

* Content > List documents

561

* Content > List document servers

562

* Content > Submit a document

563

* Content > Delete or update a document

564

565

566

(% style="color:#232c4c; font-size:26px" %)**User profiles**

567

568

Authorizations relating to user profiles have changed:

569

570

* The authorisation in previous versions**, Admin > Manage user profiles**, allows** **the user to create, edit and delete a user profile

571

* 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.

572

It is assigned by default to users who already have the **Admin > Edit a user’s attributes **authorization during migration.

573

It is also added by default to the **‘Supervisor’** and **‘System Administrator’** authorization groups//.//

574

575

=== **User settings** ===

576

577

Authorizations relating to user settings have changed:

578

579

* 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.

580

* The new authorization **‘Admin > Manage user settings’ allows **the user to create, edit and delete a user setting.

581

It is assigned by default to users who already have the authorizations**‘Admin > Edit a user’s settings’ **and **‘Admin > Manage users’ during **migration.

582

It is also added by default to the **Supervisor** and **System Administrator** authorization groups//.//

= Export =

**Tables and sort icon**

587

588

The sort icon (arrow) was not displayed or was displayed incorrectly when exporting a table.

589

For PPT and Excel exports, an arrow symbol in the same colour as the text now indicates the sort order.

590

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.

597

598

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.

604

605

606

**Changes to the structure of the //groupAcls// field**

607

608

The //groupAcls// field was previously an array of complex objects. Each object contained an identifier (id) and a sub-array of authorisations (aclList).

609

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.

610

611

(% style="width:700px" %)

612

|(% style="background-color:#f2f5f8; text-align:center; width:281px" %)**Before 2026 R1**|(% style="background-color:#f2f5f8; text-align:center; width:306px" %)**Since 2026 R1**

613

|[[image:1781791351199-303.png||data-xwiki-image-style-alignment="center"]]|(% style="width:306px" %)[[image:1781791393892-645.png||data-xwiki-image-style-alignment="center"]]

**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.

Wiki source code of Changements de comportement

Sommaire