At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Changed governed term | Select Forward impact | Connected approved artifacts | Missing links can understate impact |
| Affected retained artifact | Select Download glossary slice | Relevant frozen meanings and usages | Complete indexing is required |
| Artifact and change context | Select Download reissue handoff | External action package | The app does not edit or issue the document |
| External approval result | Preserve its reference | Release evidence context | Signature execution stays external |
How it works
- Approve the term change through the governed term workflow.
- Open the prior deposited baseline.
- Select Forward impact from the term.
- Review every affected retained artifact.
- Generate each artifact's glossary slice.
- Download the reissue handoff and send it to document control.
- Preserve the external approval reference with the release evidence.
Example
A definition change affects 18 controlled procedures. The team reviews the governed impact graph, then generates one glossary slice and handoff per retained procedure. Document-control owners revise and approve the documents in the external system. The next baseline captures the later approved state.
What this does not mean
The workflow scopes and packages evidence. It does not guarantee that every dependency is linked. It does not revise pages, approve releases, execute signatures, or replace document control.
Related questions
Next step
Complete impact review before sending any controlled artifact for reissue.
View on Atlassian Marketplace