- DATE:
- AUTHOR:
- The SafetyChain Team
Patch Release: June 9, 2026
This release includes the following fixes and improvements:
Reporting & Data Visibility
Exception report filters are now accurately applied. The system now correctly displays records based on the chosen filter criteria, ensuring more precise reporting.
Data import errors for DPT files have been resolved. The platform now handles the import of DPT files with mixed text and "N/A" values without generating errors.
Supplier Compliance
Resolved an issue where expiration date was showing in the Due date column in some scenarios. These are 2 distinct dates. Expiration date is a fixed date set by a user, and due date is a calculated date according to the Requirement configuration and set Expiration date (if configured).
Added an Expiration Date column to the Supplier Compliance > Suppliers tab table. If an expiration date is configured on a submitted requirement, it will display here. This aims to address confusion between requirement task Due Date and document Expiration Date.
Requirement Settings that impact due date of requirement tasks:
Due in = number of days after a requirement task generates that it is due
Renew in = determines number of days before an expiration that a renewal task is generated
Note: Expiration date is a fixed date set by a supplier or SafetyChain user.
Date math that determines below dates:
Scenario: New Requirement
Task Due Date = Requirement Create Date + “Due In” days
Scenario 2: Existing Requirement (renewal)
Task generate date = Expiration Date - “Renew In” days
Task Due Date = Task generate date + “Due In” days