Software update, 26 February 2025

Modified on Tue, 25 Feb at 9:33 PM


Tagging users in comments

  1. User Tagging: When writing a comment, typing the @character will trigger a dropdown list of users.
    • Dropdown Behavior:
      • The first item in the dropdown is highlighted by default (if available).
      • As you type after the @ character, the list narrows to match the string 
      • The search continues even if you type a space character.
      • If no users match the search, the dropdown shows an empty state.
      • You can navigate the dropdown using the up and down arrow keys.
      • Select a user by clicking on them or pressing Enter (which selects the highlighted user).
  2. Comment Handling:
    • Pressing the Escape key will close the dropdown, and the @ character along with any following text will become regular text.
    • Clicking the “Add comment” button while the dropdown is open will add the comment without tagging any user.
  3. Display of Tagged Users:
    • Tagged users are displayed in a highlighted fashion within the comment.
    • If no name or surname is found for the user, their email is used instead.
    • If the user does not exist, the label “Deleted or unknown user” is displayed.
  4. Email Notifications: Tagged users will receive an email notification informing them that they have been mentioned in a comment.



Label Consistency Between ESRS and Gap Analysis

  • Unified Labeling for ESRS and Gap Analysis
    • Gap Analysis now reflects the same labels as ESRS Reporting.
    • Ensured consistency at both Disclosure Requirement and Data Point levels.
  • Applied Recent ESRS Label Updates to Gap Analysis
    • Removed outdated labels, such as “DR can be excluded.”
    • Any future label updates in ESRS will also apply to Gap Analysis for uniformity.

Updated Guidance in ESRS Data Collection

  1. Replaced Guidance for ESRS Data Collection
    • Updated guidance displayed next to data points with new content.
  2. Scope of Change
    • Applied to data points in category-specific lists (G/E/S/G) for manual data collection in Step 3 of ESRS Report.
    • Updated in entity reports for aggregated data collection.
    • Reflected in data points within requests sent to collaborators.



Problem: Steps in ESRS DMA remain editable after completion.

GIVEN A DMA report with multiple steps.
WHEN 
- Step-1 fields and toggles remain editable after completion.
- In Step-1, Sustainability Matters allows survey sending after completion.
- In Step-2, IROs can be imported and surveys sent after completion.
- In Step-3, IROs can be manually assessed and collaborators added after completion.
THEN Users can modify completed steps, which should not be allowed.
FIXED BEHAVIOUR: Steps should be locked for editing once completed unless reopened.


Problem: IRO assessment page displays titles and descriptions in the wrong language.

GIVEN 
- A user opens an IRO assessment page.
- The system is set to a language other than English.
WHEN 
- The title and description are displayed in English instead of the selected language.
- Golden data IROs are affected incorrectly.
THEN The language does not match the user's current setting.
FIXED BEHAVIOUR: Titles and descriptions should always be displayed in the currently selected language.


Problem: Entity data collection status can be changed when Step 3 is closed.

GIVEN 
- A user has a slow connection.
- The user is an ESRS entity manager for an entity with at least one assigned data point in an ESRS report.
- The data collection step in that ESRS report is marked as completed.
WHEN The user opens the main questionnaire page for that entity.
THEN  The button to request approval, reopen, or close data collection appears briefly and then disappears.
FIXED BEHAVIOUR: No button allowing an entity status change should appear, even temporarily.


Implementation of Missing Taxonomy Activities

  1. Completion of Missing Activities
    • All previously missing activities have been implemented.
  2. Priority Implementation
    • Focused implementation starting with activity 14.1 in CCA.


Tracking New Events in Supplier History

What’s New?
We have expanded the supplier history tracking to include the following new events:
  • Rejecting a request
  • Accepting a request
  • Forwarding a request
Where Does This Apply?
  • These events are now tracked for all types of requests in the Supply Chain module.
  • The events can be found in the Supplier Profile History.
  • Each event will display the user who performed the action for better traceability.

Tracking events for suppliers created before 2024 

Background
Previously, supplier history tracking was only applied to suppliers created from 2024 onwards. This meant that suppliers created before 2024 did not have historical events recorded.
What’s Changed?
  • With this update, supplier history tracking is now available for all suppliers, regardless of the year they were created.
  • Events are now visible for older suppliers in the Supplier Profile History just like they are for newer suppliers.

Problem: Descriptions of Activities Are Not Translated to German in Smart Search

GIVEN a user searches for activities using the smart search function,
WHEN viewing the activity descriptions,
THEN descriptions are only available in English and not in German.
Fixed Behavior: Activity descriptions are now available in both German and English, ensuring a localized user experience.


Problem: Activities Without a Region Do Not Appear in the Region Filter

GIVEN an activity exists without an assigned region,
WHEN filtering activities by region,
THEN the activity does not appear in the filter.
Fixed Behavior: All activities without a region will now be listed under "Not Specified" in the region filter, ensuring they are still visible in searches.


Problem: Total Emissions Are Not Recalculated When Unit Is Updated for Custom Activities and Detail Screen

GIVEN a user updates the unit of a custom activity,
WHEN reviewing total emissions,
THEN the total emissions are not recalculated, and the change is not reflected in all views.
Fixed Behavior:
  • Total emissions will now be recalculated when the unit of a custom activity is updated.
  • The updated total emissions will be correctly displayed both in the custom activity view and on the details screen.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article