Simplify and clarify Platform Install experience on SCMU - #5827
Conversation
|
|
||
| var (sc, sp, audit) = sender switch | ||
| { | ||
| _ when sender == PresetMinimal => (true, true, false), |
There was a problem hiding this comment.
these presets are defined twice, it might be nice to centralise them even if it means losing the switch statement in SyncPresetSelection
|
@jpalac When I look at that image.. I don't seem to understand it.. why is monitoring not added in a full setup? Also, I don't understand the -- OR INSTALL SEPARATELY -- From an UX perspective, most users likely don't know at all what it all means. Why not list the features as big buttons where some are already selected by default?
I very much like these top buttons! However, FULL implies everything to me that feels it should be fully to the right? Maybe minimal, audit only, default, full). Just not sure if that really clear to our users. Take minimal... what would that then be? UI + primary instance? I guess for most users a UI is really required. I guess the installer could also detect if SP is already installed and based on that suggest that the UI is not required OR after installation indicate that the exiting SP install can be removed or even better an option to uninstall it? |
|
@ramonsmits Thanks for your input. We have taken some of that into consideration and are closing this PR in favour of #5837. |
Reduce the friction for the minimal install of the platform needed to provide the usage report, by making the intent of what is being installed clear from the start.
Changes based on the below mockup with a few improvements.