At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Deprecated governed term | Include it in the effective scan scope | Known non-current terminology | Deprecation must exist in the glossary record |
| Page content | Match observed use to the deprecated term | Page-linked finding | Scan scope and content availability apply |
| Finding review | Open the page and governing record | Correction context | The scanner does not edit the page |
| Corrected content | Rescan the space | New recorded state | Prior findings remain historical evidence |
How it works
- Open Compliance Scanner.
- Use Select Space to Scan.
- Select Scan Space.
- Filter for deprecated-term findings.
- Correct each affected page or governance record.
- Record the reason and rescan.
Example
A procedure still uses “data owner” after that term was deprecated in favor of “information owner.” The scan links the finding to the page and governed term. The content owner updates the procedure, then a later scan records the corrected state.
What this does not mean
The scanner reports supported matches. It does not decide whether an exception is valid, edit pages, or prove that every indirect reference was found. Reviewers own the disposition.
Related questions
Next step
Rescan after every deprecated-term correction.
View on Atlassian Marketplace