--- title: Test result and remediation task state transitions in the Configuration Compliance application description: 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\). locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/configuration-compliance/cc-state-transition.html release: australia product: Configuration Compliance classification: configuration-compliance topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Reference, Configuration Compliance, Unified Security Exposure Management, Security Operations] --- # Test result and remediation task state transitions in the Configuration Compliance application 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 **Note:** Starting with v14.9 of Configuration Compliance, the following terms have been renamed: |Terminology prior to v14.9|Terminology v14.9 onwards| |--------------------------|-------------------------| |Test Result Group|Remediation Task| |Group Rules|Remediation Task Rules| |Policy|Test group| The following table details how states and sub-states transition between configuration test results and remediation tasks.
| 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 |