History Tracking for Configurations

What is a one sentence summary of your feature request?

NDM should keep history for Configuration Changes and design modifications for portals.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

There are a lot of configurations and minor RBAC changes or policies that you can set in NDM that unless you have a habit keeping comprehensive notes on the product, you will lose track of the changes or the configurations you may have done.

Similarly, for the design node of GroupID portals, there are tons of modifications the product allows, but nowhere to keep track of.

How do you currently solve the challenges you have by not having this feature?

Save all the configurations or design settings on the One Note.

1 Like