Baseline wizard needs modeling

[ghost]

Creating/editing a baseline is pretty complex, each step essentially needing routing, without actually using a router. Currently managing which steps to move back and forth involves checking all sorts of variables; the steps are dynamic; and the sidebar only shows an indicator if we are rating a capability, so on any other step, the user has no sure idea where, in the process, they currently are.

This can be made much easier with a wizard model (not the same thing as the data model the user is creating/editing). The wizard model basically gives you your sidebar data; your current step; knowing what's next, what's previous; and keeps track of what to do with data entry ("This is bad, do I let them continue, or just flag it so they know to come back to it later?", "Oh, they selected this option, so now I have to add these steps.". "They changed a value, what else do I have to change?", etc.).

By defining this structure up front, the wizard itself simply follows the model, activating the display of the steps, highlighting the current step, activating and deactivating buttons and inputs.

[shawnbertrand]

A short term fix would be to show all mat-expansion-panels (i.e. capability groups) in the sidebar as expanded. The user would then have the ability to scroll through the entire contents of the baseline.

[ghost]

This doesn't need to be a short term fix. I put it on the next sprint so no need to do anything quick.