Page History
| Table of Contents | ||
|---|---|---|
|
What the Modernization Vector Is
For every application you keep (lifecycle vector Keep, see Lifecycle Vector: Keep or Sunset), iDNA answers two questions per modernization topic: is the application ready for the target platform, and if not, what is the most efficient way to make it ready? The answer is the modernization vector.
...
- A finding is not a crash. A finding marks code that needs review for the target, not code that is certain to break. HCL's own mail template, for example, carries Nomad code findings for features that HCL guards are guarded by design features so that they never run on Nomad.
- Readiness is per topic. The same application can be ready for Notes 64-bit and still need work for Nomad. Always check which topic you are looking at.
...
iDNA checks the routes in this order and assigns the first that applies. The dashboards use two sets of labels: the Modernization Overview shows the route as track: action, Modernization Readiness and Modernization Planning use shorter names.
| Modernization Overview | Readiness and Planning | What it means |
|---|---|---|
| Ready: No Critical Issues Identified | Ready (No Fix Needed) | Nothing to fix. Either the analysis found nothing for the target (Target Compatible As Is), or every finding sits in code of the current HCL template version (Attention Notes Available): HCL's code, not yours, so the findings stay visible as notes. |
| Template: Remediate Master | Fix Master Template | The application inherits from a master template in your environment. Fix the findings once in the master; a design refresh carries the fix to every application that inherits from it. |
| Template: Upgrade Standard | Upgrade Standard Template | The master is an unmodified HCL standard template. Don't edit it: upgrade it to the current HCL version, which already contains the fixes. |
| Template: Rebase Ancestor | Rebase Master Template | The master carries its own name but was copied from an HCL standard template, and the link was lost. Rather than fixing the old copied code, replace the master's design with the current version of that standard template and re-apply your customizations. See Template Lineage. |
| Template: Investigate Inheritance | Similar to Estate Master, Similar to Standard Template | The application inherits from no template, but its design is nearly identical (95 % similar by default) to a master in your environment or to an HCL standard template. Restoring the inheritance may fix it without touching its code. |
| Template: Unify Similar | Unify Similar Apps | The application belongs to a family of similar applications without a shared master. Unify them under one new template, so the findings are fixed once instead of per application. |
| Direct: Remediate Code | Individual Code Fixes | A genuine one-off: no template route applies, and the findings are fixed in the application itself. |
Details of the Template Routes
...
- For the big picture, how ready the estate is and whether the applications that need fixes are the ones people use: Modernization Readiness: The Estate at a Glance.
- To turn the routes into work: Modernization Planning: Work Sessions. Applications that are ready never appear there.
...