Page History
...
- What did we change back then? The code in the master's design documents compared with its ancestor: inherited unchanged, modified or added. Design changes that do not involve code are not part of this comparison.
- What survives the update? A verdict for every finding in the master: does the code disappear with the update, or does someone have to fix it?
This is the background of the routes Rebase Master Template and Upgrade Standard Template (see Modernization Vector: The Route to Ready): rather than fixing old copied code by hand, you move the master to the current HCL version, where most findings are already fixed, and re-apply only your own changes.
...
- Template Design Elements: one row per design document that carries code. [Delta Type] says whether its code is inherited unchanged from the ancestor, modified or added; by default the table shows your customizations (modified and added). [Count Custom Hashes] counts the code blocks that are not in the ancestor.
- Template Lineage Overview: how many design documents were analyzed, how many are not inherited, and the findings per modernization topic.
- Template Ancestor Overview: the ancestor and how similar the master still is to it, the template family and its newest version (the upgrade target), whether the master is only a renamed copy with identical code, and how many design versions of it run in your estate.
...
[Compared Ancestor] tells you how precise the comparison is: against a template that is scanned in your estate, iDNA compares design element by design element; against the HCL reference catalog bundled with iDNA (iDNA Reference Template), it compares code only, so added there means "all-custom code, possibly new or fully rewritten".
...