Reviewing and approving keys

Every generated key carries a status. When you complete a SmartMapper run, ReplaceMagic applies all keys with status Generated, Accepted or Modified – reviewing is optional, and newly generated keys count as approved unless you reject them. Keys marked Rejected or ForReview are never applied.

Status	Meaning
Generated	Newly produced, not yet reviewed
Accepted	Approved for use
Modified	Edited by you, and approved
Rejected	Excluded
ForReview	Ambiguous – the same search text would need different replacements in different places

Available actions

Accept all – approve everything that is not rejected. Suitable when the validation reports WouldBreak = 0 and coverage looks right.
Accept / Reject by ID – approve or exclude individual keys, given as a comma-separated list of key IDs (for example 1234,1240,1255).
Triage – bulk-approve the safest keys automatically. Two thresholds control what counts as safe: Min % is the minimum confidence a key must reach, and Min rows is the minimum number of links it must repair. Defaults of 80% and 2 mean: approve keys that are at least 80% confident and fix at least two links.
Export – write the keys to a file for review outside the application.
Finalize – recalculate coverage and confidence over the approved set only.

Your decisions survive regeneration: if you re-run SmartMapper – after adding rules, or after purchasing a licence – previously accepted, rejected and edited keys keep their status.

Suggested mapping rules

When the mapping rules check added rules, the SmartMapper wizard in ReplaceMagic shows the page Suggested mapping rules right after the keys are created. It lists each added rule with its kind (re-alignment, renamed folder, alias drive) and the evidence for it. The keys were already created with these rules.

Accept selected / Accept all – keep the rules; their origin becomes Accepted.
Delete selected – remove rules you do not want. The keys still contain them until you click Apply and recreate keys (or answer Yes when you continue to the next page). The keys are then recreated without adding suggestions again. A later normal key creation may suggest the same rule again, because the evidence is still in the scans.

Rules to check

The second list on the same page (new in 2026.2.4.0) shows your existing rules that map no scanned document and are probably wrong or not needed:

Kind	Meaning	Example
local paths	Most of the rule's links are local user or system paths (C:\Users, C:\Documents and Settings, C:\Program Files ...). Mapping them to the cloud breaks links that work on the users' computers.	c: → library root
outside scan	All of the rule's links point outside the scanned folders, so their target cannot be verified.	g: → links to G:\Risk Management
superseded	The rule mapped documents before, more specific rules map them now; it may still map a few links.	z: after z:\finance was added
unused	The rule matches no document and no link of this run.	a mistyped share name

Links is the number of links the rule maps, Files only the number of files that are changed only because of this rule. Nothing is selected or deleted automatically: select the wrong rules and click Delete selected rule(s), then Apply and recreate keys (or answer Yes when you continue). Keep a rule if its folders really were migrated to its target. Deleting an unused rule does not require new keys. Unused is not reported when the run was limited (trial or a document cap), because not all links were read.

Both lists show the full text of every column; scroll horizontally to read long evidence. Export both lists saves them in one file: in Excel one worksheet per list (Suggested rules, Rules to check), in CSV one block per list - useful to discuss the rules with the people who ran the migration.

If no rule was suggested and there are no rules to check, the page is skipped.