Software updates, 27 January 2025

Modified on Sun, 26 Jan at 5:29 PM



Yay, another week with exciting software updates from Daato! Scroll down and learn more about the new developments on the platform:





We have brought some improvements to the ESRS Gap Analysis feature, this is how it looks like:


What has changed?


  1. Labels for Data Points:
    • In a Gap Analysis report, data points and disclosure requirements now display blue labels similar to those used in ESRS report.
    • Data points with the category "Voluntary" will show the label “Voluntary”.
    • Data points with the category "Phase-in" will show the label “Phase-in”.
    • Both labels can be displayed simultaneously if both conditions are met.
  2. Information Tooltips:
    • All labels have an information icon that displays a tooltip with an explanation when hovered over.
    • Each type of label has a distinct explanation.
  3. Justification Modal excluding Phase-in Data Points is added:
    • A new confirmation/justification modal has been introduced for phase-in data points.
    • This modal includes a field for providing justification.
    • The confirm button is only active when the justification field is populated.
    • Justifications are stored, and a history event is created when excluding the data point, similar to other data point categories.
    • The modal has separate translations from the regular
  4. Simplified Data Point Categories:
    • The "required" category for data points has been removed.
    • Data points can now only be marked as “Not Material,” “Voluntary,” or “Phase-in”.
    • Labels exist only for “Voluntary” and “Phase-in”. All other data points that are not Voluntary or Phase-in can be marked as not material and excluded by default.





We added the possibility to not just invite existing users, but also all stakeholders to assess IROs in the Double Materiality Assessment:


  1. When sending collaboration request for the whole IRO assessment or any of data points included in it, stakeholders are included on the data providers' list
    • They are shown on top of the list under group: “Internal stakeholders” and "External stakeholders"
    • Users that get shown below then have a headline called "Users"




  1. Addition of Upload Box:
    • A new box has been added at the bottom of the DMA Step 1 page, below the survey.
    • The box is titled "Provide additional context".
    • The box contains the text: "Upload any documents that help understand the context analysis that you have conducted for this step."
  2. More Information Button:
    • A "More information" button has been added, which leads to the helpdesk
  3. Drag and Drop Field:
    • A drag and drop field has been included for easy document upload.
  4. Datapoint History:
    • The system now tracks who uploaded and deleted documents, along with timestamps.





Improved ranking of sustainability matters in the Double Materiality Assessment

In the DMA Results page, in Ranking view the sustainability matters are now ranked based on their highest materiality (financial or impact). Previously it was ordered by the sum of financial and impact materialities. E.g. if Sustainability Matter 1 has financial materiality assessed as high (3) and impact as non-material (0), it will be higher than Sustainability matter with both financial and impact materialities at medium (2).
This is because Max(3, 0) > Max (2, 2)
Previously the latter would be shown higher, as (2 + 2) > (3 + 0)





"DR can be excluded" label removed:

  1. Label “DR can be excluded” is not displayed anymore under any DR in Step 1
  2. Only label is removed, but definitions stay intact and the behaviour of the DRs stays the same.


Uploaded IROs with manual assessment not shown as assessed:

Problem
GIVEN an IRO was created via the import feature
AND in the import file it had the manual assessment value provided
WHEN the results in step 4 of the DMA report are shown
THEN that IRO is shown as not assessed
Fixed behaviour
…that IRO is shown as assessed with the value provided in the import file (unless user changed it in the meant


Request not sent to some stakeholder in DMA survey
Problem

WHEN survey is sent in DMA
THEN some stakeholders included in it do not receive a request
Fixed behaviour
…all stakeholders in that survey receive a request (and the requests are recreated for the already sent surveys)

When adding attachments to IRO assessment datapoints the value disappears

Problem
GIVEN a value for description, impact type (Negative/Positive), impact actuality (Actual/Potential) was given when creating that IRO
WHEN an attachment is uploaded to one of these data points in IRO assessment
THEN the value is overwritten by empty value (but only in report, the old values are still there in the IRO object)
Fixed behaviour
  1. Uploading attachments (or adding comments) doesn’t remove the original value
  2. For all instances all original values (stored in the IRO object) are restored if:
    1. an attachment was uploaded (or comment added - please check if this affects these data points too) for a data point
    2. the value is currently empty in the report



This new status refers to suppliers whose code of conduct takes place within the last 30 days before it expires. This is a helpful feature especially when updating the expiry date of CoC in bulk - which is the second feature in this release.  


The new status can be selected from the Filter in Repository. The steps are:
  1. Go to Repository 
  2. Then open the Filter
  3. Go to Code of conduct filter 
  4. Now select from the dropdown" Expiring soon" 



It's possible to select multiple suppliers in the repository and set the expiry date of Code of Conduct in bulk without having to do that for individual suppliers. 
 
How it works:
  1. Select suppliers in repository in bulk 
  2. Click on Actions 
  3. From the dropdown, you can find the action "update expiry date"


Updating expiry date in bulk will update the date for suppliers whose Code of Conduct has been already accepted.



Problem: FE fixes in the History tab in supplier profile:

Fixes include: Translations, showing BE endpoints when displaying the requests events, receiving a succss message in History without updating anything 


CoC expiry date missing in repository if the CoC status is updated to complete in the Excel import file:

GIVEN the COC status is set to "complete" in the Excel import file,
WHEN the data is imported into the repository,
THEN the COC expiry date is missing from the supplier profile.
Fixed Behaviour: The COC expiry date will now be displayed in the supplier profile if the COC status is set to "complete" in the import file. The expiry date is automatically calculated as one year from the date of importing the supplier.

Bulk action - Assign sourcing entity - search not working:

GIVEN users attempt to assign suppliers a sourcing entity through bulk action,
WHEN the search field is used to find suppliers,
THEN the search does not function as expected, preventing users from efficiently locating suppliers.
Fixed behavior: The search field in the "Assign sourcing entity" bulk action now functions as expected. Users can accurately search and locate suppliers for assignment.



Emission factor is not displayed in the overview when adding activities using smart search:


GIVEN a custom activity or an activity is added via smart search,
WHEN viewing the activity overview in the first step of a CO2 report,
THEN the emission factor is not displayed.
Fixed behavior: The emission factor will now be displayed in the activity overview when adding a custom activity or an activity via smart search. This functionality is applied to the first step of the CO2 report.

Wrong calculation of total emissions:


GIVEN total emissions are calculated in reports,
WHEN the system processes the relevant data,
THEN the total emissions are calculated incorrectly.
Fixed behavior: Total emissions should be calculated correctly. 

Table is set to the first page when opening an emission factor in the side drawer:


Fixed behavior: If user opens an emission factor in the emission factor database tab, the page of the table will persist and not jump to the first page as before. 


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