Record affected and repaired version sets
Synthetic known issue K-321 affects v4 and v5; a verified repair is available only in v6. Guide W-321 remains relevant to v4/v5, while v6 should use its verified normal procedure N-321. Publishing v6 does not show that every customer upgraded. The fixture maintains applicability by the customer’s confirmed build, and treats an unknown build as a review case. No automatic product upgrade is implied.
| Customer build | Issue evidence | Guide treatment | Next action |
|---|---|---|---|
| v4 | Still affected | Keep W-321 applicable | Use verified workaround conditions |
| v6 | Repair verified | Use N-321; retire W-321 for v6 | Check customer normal task |
| Unknown | Build not established | Do not choose either by assumption | Establish build |
Update guidance by confirmed applicability
- Read affected and repaired builds
- Confirm customer build
- Choose current procedure for that build
- Retain older applicable guidance
If the verified repair excludes a configuration, keep that exception visible in the normal procedure.
Can W-321 be retired for a confirmed v4 customer because v6 exists?
Show the worked answer
No. v4 remains in the affected set. A v6 repair does not change that customer’s build or remove their need for the applicable workaround.
Retain guidance for still-affected confirmed builds. Planned upgrades need confirmation before the customer's applicable procedure changes.