01/09/2025 - Despite the holiday season, this year’s summer brings several new functionalities

To ensure the full alignment with the DPM models of the EBA, the SRB and many national regulators, we have improved/introduce the functionality of reusing tables and business rules from other (typically previous) framework versions. When copying a table or business rule between framework versions user can decide if to paste it as a new object or reuse the object from the other framework version exactly as it is defined there. This shall help with quality assurance of models by regulators (where regression testing of the reused content can be simplified) as well as the regulated entities consuming models to clearly understand the content that has changed between the releases. Please note that the export to XBRL of reused tables and business rules is still in development/under testing. We are also working on the ability to reuse table groups.

We have also improved the way users interact with the list of business rules, where bulk actions were introduce enabling users make multiple changes to a selected subset of business rules as well as to bulk copy, paste and delete. This brings to the UI functionalities that so far were available only through the manual update to the Excel file with business rules for reimport.

It is now also possible to export to XBRL models according to the DPM 2.0 XBRL architecture i.e. to produce a fully valid taxonomy package following the latest EBA publications. We have also improved interaction with the DPM 2.0 models by better presenting the Release information in modelling of tables.

When exporting to XBRL users are now also able to decide if to use the compact version of the definition linkbase of tables i.e. reusing hierarchies from dictionary rather than duplicating their content. This works for the DPM 2.0 XBRL architecture by default but can be applied also for the DPM 1.0.

Users can also decide to auto-generate filing indicator checks attached to each module schema file to ensure that the declared in a report filing indicators follow the allowed values for each module based on their content i.e. referred tables.

Ability to decide if a domain is nillable or not can be now set on each domain individually but can also be overridden in the XBRL export wizard to enable backwards compatibility of serialisation to this format.

We have also added a new function existanceAssertion() enabling checking of presence of mandatory data in reports (according to XBRL existence assertions specification) regardless of the declared filing indicators and support for xff:has-fallback-value where using isfallback() function users no longer need to assign variables as sequences in case they want to check their presence.

There is now also automated match between facts in business rules in case some of them are instant while others are duration (by means of instantDuration filter applied automatically on instant variables pointing to duration variables).

We have also made many technical improvements to ensure better performance of the platform (e.g. by reducing the number of API request happening in the background, recalculating information on the front end, etc), increase stability (update to databases) and to support regression testing (e.g. sorting of modules in taxonomy package, sorting of filters in XBRL assertions, sorting of references between XBRL taxonomy files, etc).

Any we fixed many bugs in the application itself (e.g. navigation between sections) as well as in its exports (e.g. global dimensions in XBRL assertions repeating on matchDimension filters, Annotated Templates missing parent owners in prefixes, etc.)