{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":43706,"path":"security-management/configuration-compliance/cc-state-transition.md","title":"Test result and remediation task state transitions in the Configuration Compliance application","bundle":null,"doc_type":null,"release":"australia","body":"\n# Test result and remediation task state transitions in the Configuration Compliance application\n\nThe 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\\).\n\n## State transition scenarios between test results and remediation tasks\n\n**Note:** Starting with v14.9 of Configuration Compliance, the following terms have been renamed:\n\n|Terminology prior to v14.9|Terminology v14.9 onwards|\n|--------------------------|-------------------------|\n|Test Result Group|Remediation Task|\n|Group Rules|Remediation Task Rules|\n|Policy|Test group|\n\nThe following table details how states and sub-states transition between configuration test results and remediation tasks.\n\n<table id=\"table_eyp_43m_w1c\"><thead><tr><th>\n\nIf a remediation task state transitions from...\n\n</th><th>\n\n...to state/sub-states\n\n</th><th>\n\nIts associated test results states transition from...\n\n</th><th>\n\n...to state/sub-states\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nOpen\n\n</td><td>\n\nUnder Investigation\n\n</td><td>\n\nOpen\n\n</td><td>\n\nUnder Investigation\n\n</td><td>\n\nStates transition bi-directionally.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nIn Review\n\n</td><td>\n\nOpen\n\n</td><td>\n\nIn Review\n\n</td><td>\n\nStates transition bi-directionally.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nDeferred/with any reason selected for Resolution\n\n</td><td>\n\nOpen\n\n</td><td>\n\nDeferred\n\n</td><td>\n\nTest results keep the same reason for Resolution as the remediation task.\n\n</td></tr><tr><td>\n\nDeferred/with any reason for Resolution\n\n</td><td>\n\nOpen\n\n</td><td>\n\nTest results remain Deferred\n\n</td><td>\n\n \n\n</td><td>\n\nTest results keep the same Resolution as the remediation task.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nResolved/ Fixed\n\n</td><td>\n\nOpen\n\n</td><td>\n\nResolved\n\n</td><td>\n\nStates/sub-states transition bi-directionally.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nResolved and Resolved to Closed/Fixed\n\n</td><td>\n\nOpen\n\n</td><td>\n\nResolved\n\n</td><td>\n\nIf 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.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nResolved\n\n</td><td>\n\nOpen\n\n</td><td>\n\nResolved\n\n</td><td>\n\nStates/sub-states transition bi-directionally.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nResolved/Cancelled\n\n</td><td>\n\nOpen\n\n</td><td>\n\nResolved\n\n</td><td>\n\nStates/sub-states transition bi-directionally.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nResolved and Resolved to Closed\n\n</td><td>\n\nOpen\n\n</td><td>\n\nResolved\n\n</td><td>\n\nIf a remediation task transitions to Closed automatically, its associated test results can transition back to Open.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nResolved and Resolved to Closed/Result Invalid\n\n</td><td>\n\nOpen\n\n</td><td>\n\nResolved and Resolved to Closed/Result Invalid\n\n</td><td>\n\nIf a remediation task transitions to Resolved it can transition back to Open.\n\n If a remediation task transitions to Closed/Result Invalid, it and its associated test results cannot be reopened.\n\n</td></tr><tr><td>\n\nOpen\n\n</td><td>\n\nClosed/Fixed\n\n</td><td>\n\nTest results remain Open\n\n</td><td>\n\n \n\n</td><td>\n\n \n\n</td></tr></tbody>\n</table>**Note:**\n\n-   Starting with v14.12 of Configuration Compliance, the **Result invalid** option is removed in the **Resolution** field in the Close modal.\n-   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.\n\n"}}