Professor
Product Manager
We're not currently looking into a way to "stitch" data across module name change updates, but we are working on a feature that would let you easily update and keep your changes to:
-AppliesTo
-AD/Collection intervals
-AD Filters
-Alert threshold changes
It would be very similar to the Group/Device/Instance level Alert Threshold tuning we allow now, but we would extend it to the account-level, and add the above. This means that for core LogicModules, you would just update the main definition, and apply your tweaks on the Device tree.
I know that doesn't solve the stitching problem, but it should make merge/updates easier, and would not require the use and management of clones.
We also looked into a more advanced diff & merge option, but generally we know if you changed one of those things above, you want to keep it when updating.
Changing something not listed above would require creating a new module definition.
The great thing about this approach is that minor changes to the module don't result in a brand new module that you have to clone or manage.
If you make frequent customizations to things not on that list, or you already have a lot of clones, there may be some pain in migrating to the new paradigm.
This doesn't preclude further enhancements in the future, but we think this is a good iteration that will save lots of time with updates going forward. Any feedback is appreciated.
