What is the challenge? |
When applying a workspace template, even if the settings are marked as unlocked in the template, once applied to a workspace the existing workspace settings will still be changed. This is not always the desired experience. If I have a field unlocked, I may want that team to maintain their current customization (for example, their custom terminology). |
What is the impact? |
The template always overriding settings (like layouts) means that applying a workspace template can involve a lot of change management for current teams. They will need to go back in and update their workspace settings to re-add their customizations. If I just want a few settings maintained across workspaces, a template does not make this easy and will cause unwanted settings updates. |
Describe your idea |
Setting on workspace template to set specific areas to not override existing settings when applied. |
Since established scorecard values will be lost if the destination workspace scorecard configuration differs from the template scorecard configuration, this prevents us from moving pre-existing workspaces onto our template - which increases our workload every time we want to roll out any template based automation, etc. and effectively defeats the purpose of even having a template.