Read the role-code transition
Fictional role R-OLD retires at start day 20 with approved mapping to R-NEW for active assignments. Active S33 and S34 use R-OLD; historical day 10 report for S35 also uses R-OLD. Local transition updates active records, retains historical codes and blocks new R-OLD selections after day 20.
| Record | State | Action |
|---|---|---|
| S33 assignment | Active R-OLD | Map R-NEW |
| S34 assignment | Active R-OLD | Map R-NEW |
| S35 day 10 report | Historical R-OLD | Retain |
Update current associations only
- Verify approved mapping identity
- Change two active assignments
- Retain historical R-OLD reference
- Disable new old-code selection
An unmapped active role remains an exception rather than being assigned an arbitrary new role.
How many assignment records change and historical records remain?
Show the worked answer
Two active assignments change; the one historical report remains R-OLD. No past report is relabelled R-NEW.
Preserve historical code meaning
| Case | Action or result | Evidence boundary |
|---|---|---|
| Map all three rows | Reject historical rewrite | S35 report predates transition |
| New R-OLD selection on day 20 | Reject under local rule | Retired from day 20 start |
Keep mapping revision and counts beside the transition event. A changed display label alone does not demonstrate that active coded associations were updated.