Page History
...
Each session kind follows from a route of the modernization vector:
| Session | Works on | The work |
|---|---|---|
| Fix Master Template | a master template | Fix the master once; the applications inheriting from it are fixed with a design refresh. |
| Rebase Master Template | a master derived from an HCL standard template | Replace its design with the current version of the standard template, then re-apply your customizations. |
| Upgrade Standard Template | an HCL standard template | Upgrade the master to the current HCL version instead of editing it. |
| Unify Similar Apps | a design family | Investigate building one shared master for a family of similar, unlinked applications. |
| Investigate Inheritance | the template the applications resemble | Verify or restore the template relationship, then bring the applications onto the fixed master. |
| Individual Code Fixes | one application | Fix a standalone application in place. |
Unify Similar Apps and Investigate Inheritance sessions need a human decision first: can the applications really share one template? Until that is decided, the applications they would make ready are a potential, not a certainty. "Not reconcilable" is a legitimate outcome.
...
- Master first, then the refresh, then the applications. Fix the master before you refresh the applications that inherit from it.
- A refresh overwrites diverging application code. Decide about every Resolve Divergence item before the refresh; fix the remaining application code after it.
...
- [Modernization Topic]: the target platform; the dashboard opens with Notes 64-bit.
- [App Usage in Last 90 Days?]: on the Planning Summary tab, limits the charts to applications used in the last 90 days (Yes) or not used (No). The bar chart applies it per session: Yes keeps every session with at least one recently used application.
- [Session Details]: the selected session on the Work Session Overview tab. You set it by clicking a session title.
...
- Applications that need fixes by Modernization Vector: the donut chart shows how the applications that still need fixes divide between the routes.
- Work Items by Work Kind and Modernization Vector: for each kind of session, the number of work items, split by work kind. Author Fix, Apply Authored Fix and Resolve Divergence are code work; Cleared by Template Update and HCL Owned need no code fix.
Work Session Overview Tab
...
The product's own explanation: the session kinds, how the plan is calculated, and what each key number means.
...
- Work the sessions from the top. A code block you meet further down is either written there or was already fixed in an earlier session (Apply Authored Fix).
- For the code work of a session: Modernization Session Work List.
- Before you rebase a master: Template Lineage shows what was customized and what survives the update.
- For all sessions of one route in a single list: Modernization Overview by Work Session.
...