Forbid / discourage user from leaving DESCRIPTION field unchanged
The “DESCRIPTION” field is meant to be used as a description for the changes in the new key being created vs the previous key
In all use cases - or at least all that I can think of (I am not familiar with some L1 DOC workflows) - the DESCRIPTION field should change when a new row is created
So, when the description field has not been edited, the new L1CE should either
- forbid a new key from being “saved” until the description field is changed, or
- provide an automatically-generated default description that lists the sub-keys that have been changed, announced through some box that pops up when the “SAVE” button is clicked. N.B. The current L1CE automatically generates the description field for the new key, which the user can then edit - so the same description-generating algorithm could be used in the new L1CE.
If anyone else thinks of some workflows where the "DESCRIPTION" should not be changed when creating a new key, then we would need the option for the user to click a button some pop-up box to confirm that they want the DESCRIPTION field to stay the same. (The ost important thing is to make sure users don't just accidentally forget to edit the DESCRIPTION field)