---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/security-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Test result and remediation task state transitions in the Configuration Compliance application

# Test result and remediation task state transitions in the Configuration Compliance application {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

The states of configuration test records and their associated remediation tasks (RTs) are impacted if test result records are deferred, resolved, reopened, and transferred to other remediation efforts (REs).

## State transition scenarios between test results and remediation tasks {#cc-state-transition__section_vnx_rgm_w1c}

Nota:  
Starting with v14.9 of Configuration Compliance, the following terms have been renamed:{#cc-state-transition__section_vnx_rgm_w1c__entry__2}

| Terminology prior to v14.9 | Terminology v14.9 onwards |
|-|-|
| Test Result Group | Remediation Task |
| Group Rules | Remediation Task Rules |
| Policy | Test group |
[Tabela 1. Changes in terminology]

The following table details how states and sub-states transition between configuration test results and remediation tasks.
{#cc-state-transition__table_eyp_43m_w1c__entry__5}

| If a remediation task state transitions from... | ...to state/sub-states | Its associated test results states transition from... | ...to state/sub-states | Description |
|-|-|-|-|-|
| Open | Under Investigation | Open | Under Investigation | States transition bi-directionally. |
| Open | In Review | Open | In Review | States transition bi-directionally. |
| Open | Deferred/with any reason selected for Resolution | Open | Deferred | Test results keep the same reason for Resolution as the remediation task. |
| Deferred/with any reason for Resolution | Open | Test results remain Deferred |   | Test results keep the same Resolution as the remediation task. |
| Open | Resolved/ Fixed | Open | Resolved | States/sub-states transition bi-directionally. |
| Open | Resolved and Resolved to Closed/Fixed | Open | Resolved | If a remediation task transitions to Closed/Fixed, it can transition back to Open. If the task transitions to Open, its associated test results transition from Resolved back to Open. |
| Open | Resolved | Open | Resolved | States/sub-states transition bi-directionally. |
| Open | Resolved/Cancelled | Open | Resolved | States/sub-states transition bi-directionally. |
| Open | Resolved and Resolved to Closed | Open | Resolved | If a remediation task transitions to Closed automatically, its associated test results can transition back to Open. |
| Open | Resolved and Resolved to Closed/Result Invalid | Open | Resolved and Resolved to Closed/Result Invalid | If a remediation task transitions to Resolved it can transition back to Open. If a remediation task transitions to Closed/Result Invalid, it and its associated test results cannot be reopened. |
| Open | Closed/Fixed | Test results remain Open |   |   |
[ ]

{#cc-state-transition__table_eyp_43m_w1c}  
Nota:  
* Starting with v14.12 of Configuration Compliance, the Result invalid option is removed in the Resolution field in the Close modal.
* Starting with v14.12 of Configuration Compliance, the Remediation Task State Approval workflow is deprecated and replaced by the flow Remediation Task State Approval in the flow designer.
{#cc-state-transition__ul_qbv_nty_dcc}