Within the Nullstone UI, there are times that configuration changes are not available and the easiest solution is to login into the provider console and make the changes manually, however these manual edits can be over-ridden when the module is relaunched or upgraded. Often times, the user who made the edits may not recall the manual configuration changes or a new user is unaware of those changes.
Intended Outcome
A feature to allow a user to create notes/checklists in regards to the manual edits they performed. This note/checklist feature would allow the user to lock the current module to prevent the module upgrade/relaunch. The unlocking of this feature would create an alert or assign the task of performing the manual entries to the user after the upgrade/relaunch. Since this requires a user to perform the tasks after relaunch, this would in essence provide an audit trail or followup requirements.
How will it work?
Within the configuration tab, a checkbox-"Configuration Options not provided within this Tab can be manually implemented in the provider console -- Would you like to create a checklist of those changes?"..... provides a user a way to document those changes. In addition, user can select the module be locked for further relaunch unless an alert or checklist is persisted in the UI to provide an after launch checklist.
Summary
Within the Nullstone UI, there are times that configuration changes are not available and the easiest solution is to login into the provider console and make the changes manually, however these manual edits can be over-ridden when the module is relaunched or upgraded. Often times, the user who made the edits may not recall the manual configuration changes or a new user is unaware of those changes.
Intended Outcome
A feature to allow a user to create notes/checklists in regards to the manual edits they performed. This note/checklist feature would allow the user to lock the current module to prevent the module upgrade/relaunch. The unlocking of this feature would create an alert or assign the task of performing the manual entries to the user after the upgrade/relaunch. Since this requires a user to perform the tasks after relaunch, this would in essence provide an audit trail or followup requirements.
How will it work?
Within the configuration tab, a checkbox-"Configuration Options not provided within this Tab can be manually implemented in the provider console -- Would you like to create a checklist of those changes?"..... provides a user a way to document those changes. In addition, user can select the module be locked for further relaunch unless an alert or checklist is persisted in the UI to provide an after launch checklist.