---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Create Digital Resilience Incident form

# Create Digital Resilience Incident form {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

On the Create Digital Resilience Incident form, fill in the fields.
{#create-new-dig-res-inci__table_uj1_q5x_nvb__entry__2}

| Field | Description |
|-|-|
| Number | Number of the case. This field is automatically set. For example, DRI000108. |
| Name | Name of the incident. For example, <kbd class="ph userinput">DRI Case 1</kbd>. |
| Description | Description of the incident. |
| State | Workflow state of the incident. This field is automatically set to Draft. |
| Type | Nature or type of the incident. This field is automatically set to Digital Resilience Incident Case. |
| Subtype | Sub type of incident. For example, Documentation Loss. |
| Assignment ||
| Requester | Person who reported the incident. |
| Assignment group | Group assigned to the case. Note: The assignment group is preconfigured to the case type during configuration setup. |
| Approvers | Approvers of the incident. |
| Requested on behalf of | Name of the person on whose behalf you've created the incident. |
| Analyst | Analyst who analyzes and works on the incident. The analyst is a part of the Assignment group. |
| Watch list | People who must be aware of the incident. |
| Primary origin ||
| Source | Source of the case. This field is automatically set to Manual when the reporting case is manually created. |
| Schedule ||
| Date of discovery | Date that the case is discovered by you. For example, the case may have occurred on 18-02-2024, but is discovered by the user only on 12-03-2024. |
| Date of occurrence | Date that the case occurred on. For example, the case may have occurred on 18-02-2024. |
| Closed date | Date that the case is closed on. |
| Reported date | Date that the case gets reported on. |
| Pending approval start date | Date that the case was resolved on. |
| Approved date | Post case review date of the case. |
| Reporting status ||
| Regulatory reporting status | Primary cause of the case occurrence. Available options are: * Potentially reportable * Reportable {#create-new-dig-res-inci__ul_zyj_214_ydc} |
| Regulatory area | Digital Operational Resilience Act |
| Activity ||
| Work notes (Private) | Notes or information regarding the case. |
| Comments (Customer visible) | Additional information regarding the case for the customers. |
| Email | Option to compose an email about the case to the stakeholders. |
| Attachments | Option to attach the PDF of the case. |
[Table 1. Create Digital Resilience Incident form]

{#create-new-dig-res-inci__table_uj1_q5x_nvb}