EQS-Updates 22. May 2025 :

❗ Problem:

User could not be added to the EU Taxonomy module because the invitation email was not sent.

GIVEN:

An user attempts to set up a new user for the EU Taxonomy module

AND provides a valid email address

WHEN:

The user creation is submitted

THEN:

The system fails to send the invitation email, preventing the new user from accessing the module

✅ Fixed Behavior:

Invitation emails are now correctly triggered and sent when a user is added to the EU Taxonomy module.

❗ Problem:

Sending requests to suppliers fails with a back-end error.

GIVEN:

A user initiates a supplier request via the platform

AND the request is correctly filled out

WHEN:

The user attempts to send the request

THEN:

The software throws a back-end error and the request is not sent

✅ Fixed Behavior:

Requests to suppliers are now sent successfully without triggering back-end errors.

❗ Problem:

Supplier contacts cannot reply to requests despite having the correct role.

GIVEN:

A user has an Admin role

AND is assigned as a supplier contact

AND receives self-assessment and Code of Conduct requests for "Own Business"

WHEN:

The user tries to reply to these requests

THEN:

They are unable to respond, even though they are the intended recipient

✅ Fixed Behavior:

Supplier contacts with the appropriate role and assignment can now respond to self-assessment and Code of Conduct requests as expected.

❗ Problem:

Clicking “Accept Request” as an entity manager has no effect.

GIVEN:

A user is assigned as an entity manager for a specific entity

AND receives a request to accept

WHEN:

The user clicks “Accept Request”

THEN:

Nothing happens and the request remains unaccepted

✅ Fixed Behavior:

Assigned entity managers can now successfully accept incoming requests.

❗ Problem:

Column names in the repository settings are not translated when the platform language is German.

GIVEN:

A user sets the platform language to German

AND navigates to the repository settings

WHEN:

The user views the column names

THEN:

Column names remain in English instead of appearing in German

✅ Fixed Behavior:

All column names in repository settings are now correctly translated when the platform language is set to German.

❗ Problem:

Missing titles and descriptions for individual IROs in the assessment questionnaire view, even though this data is present in the system.

GIVEN:

A user is viewing an assessment questionnaire that includes multiple IROs, each of which has a name and description entered in the backend.

WHEN:

The user navigates to the assessment page to review an individual IRO, such as "E2 - Air pollution - Access to incentives and tax benefits, Improved competitiveness".

THEN:

The IRO's name and description do not appear on the assessment page, despite being correctly populated in the system.

✅ Fixed Behavior:

The IRO’s name and description should be correctly retrieved and displayed on the assessment page for each relevant IRO.

❗ Problem:

The warning toast on Step 2 of the DMA report is not translated when the selected language is German.

GIVEN:

A user has created a DMA report and sent the Step 1 survey without completing it, with the application language set to German.

WHEN:

The user attempts to complete Step 1 and proceed to Step 2.

THEN:

A warning toast is displayed in English ("Warning") instead of German.

✅ Fixed Behavior:

The warning toast should be localized and display "Achtung" when the selected language is German.

❗ Problem:

Percentage calculation in ESRS is incorrect for aggregated data — values are wrongly inherited by child entities without input.

GIVEN:

Entity 1 is a parent of Entity 1.1

AND the following data points are filled in for Entity 1:

- (E1-5 37) What is your total energy consumption related to own operations?

- (E1-5 37 b) What is your total energy consumption from nuclear sources?

AND this results in the automatic calculation of:

- (E1-5 AR 34) What is your percentage of energy consumption from nuclear sources in total energy consumption?

AND no values are entered for data points (E1-5 37) and (E1-5 37 b) for Entity 1.1

WHEN:

The data point (E1-5 AR 34) is viewed at the top-level (e.g., by clicking “View progress” and opening the modal)

THEN:

The data point for Entity 1.1 incorrectly shows the same calculated value as Entity 1, even though no input was provided for Entity 1.1.

AND WHEN:

The data collection questionnaire for DR E1-5 is displayed for Entity 1.1

THEN:

The value for data point (E1-5 AR 34) is prefilled with the value from Entity 1, despite missing input values in Entity 1.1.

✅ Fixed Behavior:

- The value for Entity 1.1 should remain **empty** unless manually entered.

- The top-level value of data point (E1-5 AR 34) should be automatically calculated as:

(sum of all (E1-5 37 b) values) ÷ (sum of all (E1-5 37) values) × 100,

using only data from entities where at least (E1-5 37) is filled in.

❗ Problem:

ESRS Step 4 page fails to load (shows blank screen) for users with the ESRS Reporter role.

GIVEN:

The user has the role ESRS Reporter

AND is assigned to a disclosure in an ESRS or ESRS-Lite report

AND the report is in Step 4, with Steps 1, 2, and 3 completed

WHEN:

The user opens the report

THEN:

The report page fails to load and displays a blank screen.

✅ Fixed Behavior:

The user should see the 4th step of the report, displaying only the disclosures they are assigned to, as expected by their role.

❗ Problem:

Clicking "Accept" on a request does not update the request status — no action is triggered.

GIVEN:

A user is on a customer-specific instance of the platform

AND a request is in review status

WHEN:

The user clicks the "Accept" button to approve the answer

THEN:

Nothing happens — the status does not change, and the request remains in review.

✅ Fixed Behavior:

Clicking "Accept" should successfully update the request status from review to complete.