A list of findings per application does not tell you where to start. What you need is a plan: "Fix this template first, it makes a third of the applications ready. These ten similar applications should become one template. What remains are a few one-off fixes." Modernization Planning turns the modernization vectors (see Modernization Vector: The Route to Ready) into exactly that: a ranked queue of work sessions for one modernization topic.
Notes designs cannot be rewritten reliably by a program: every fix means a developer in Domino Designer with one design open. A work session is therefore one design fixed completely in one sitting: a master template, a family of similar applications, or a single application. While the design is open, everything in it is fixed, so nobody has to open it twice.
The sessions are ranked by what they achieve: first by the number of applications the session alone makes ready, then by the number of applications it affects, then by their usage. A session that makes 20 applications ready comes before one that makes a single application ready.
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.
Inside a session, every code block with findings is a work item, and every work item says what it needs:
Every session comes with its procedure, in order. For a rebase, for example: back up the master, replace its design, re-apply your customizations, verify that the cleared findings are gone, review the HCL notes, point the member applications at the master and refresh them, re-scan. Two rules apply to every session:
iDNA locates and quantifies the work, and the work itself happens outside iDNA: your developers or administrators carry it out in Domino Designer and Domino administration. iDNA does not track the progress of a session. Once the changed designs have been scanned again, the next nightly run updates the vectors and the plan.
In the iDNA Portal: [App Lifecycle] → [Modernization Planning].
The sessions in order of their rank. The session title is a sentence that names the work, for example Rebase master acme_StdR9Mail onto StdR9Mail lineage (99% similar) or Remediate 'InternalApp Acme0024649' in place. Scroll the table to the right for the key numbers: the number of applications, the usage the session clears (user access days in the last 90 days of the applications only this session makes ready) and the blocks to fix.
Click a session title to show its details on the right:
Click the session title again to clear the selection.
The product's own explanation: the session kinds, how the plan is calculated, and what each key number means.
|
The iDNA Applications Companion can walk you through a session. Ask, for example, "Walk me through the session 'Rebase master acme_StdR9Mail onto StdR9Mail lineage': what do we do, step by step?" The Companion lists the steps in order and puts the code blocks under the step they belong to, tells you which blocks are real work and which are only notes, and warns you where a refresh would overwrite code. You can also ask "Which sessions should we do first for Notes 64-bit, and why?" See Setting up the iDNA Applications Companion. |