> For the complete documentation index, see [llms.txt](https://docs.doraedge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doraedge.com/release-notes/5-august-2025.md).

# 5 August 2025

## Released 5 August 2025

### Summary

This release includes a couple new features to improve continuous ICT-network monitoring, compliance operations and incident reporting requirements.  

#### Incidents

1. Rolled out "relaxed" reporting time limits for Incidents categorized as "Non-major."
2. Description allows for "returning" for paragraph formatting.

#### **Contracts**

1. Introduced Contract "Statuses" 
   1. **Active** and **Expired** statuses are automatically assigned based upon the **Contract End Date.** 
   2. Contracts can now be **Archived** and **Restored** for the purposes of including or excluding them from the Register of Information report. Archived Contracts require inputting a reason.
   3. Added a **Renew** Contract feature on Expired Contracts which creates a Draft Contract that maintains all Contract details.
2. Navigation / Usability
   1. Updated the Relationship duplication feature to include a shortcut for "Service Type."
   2. Separated pages for Draft and Archived Contracts. 
   3. Added filtering of Contracts in table lists by Status and End Date.
   4. Parent contracts are now linked and accessible via associated Contract records.
   5. Validation in Contract form to ensure that all Contracts have unique Reference Numbers.

#### **General Form updates**

1. "Save without changes" and "Exit" buttons on all forms
   1. Forms show an “Exit” button when a record is both created, and a previously saved version is edited. “Save without changes” appears in the final step to close the form when no edits were made. 
   2. *Exceptions: Contract forms and Incident Reports have "Exit and Save Drafts."*
2. Linked Records
   1. Show only Active data (e.g., draft Contracts are not displayed).
   2. Include related Incidents on Provider cards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.doraedge.com/release-notes/5-august-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.