We have several business units in our company and most of them need to identify specific custom attributes that only make sense to them. So rather than having a bunch of custom fields displayed that confuse or clutter up a page, we’ve assigned those business units to their own dedicated Context User Group so that we can make page configurations dedicated to how they function and view their data. But since its highly recommended that you never modify the global context, if we add a custom attribute to a page that everyone should have we repeat that page configuration for each context user group.
So I’m looking to see if setting up a COMPANY defined context mapping is viable. If we make configurations to a page that is needed by all business units we assign them to a Company Context so all users would see it and wouldn’t have to repeat those configurations as well as re-baseline them. Problem that then occurs is no other PC can be assigned to a different context on this page.
Curious if anyone else has done this and if there is another option that could be added to the mapping condition to avoid the inability to add future context mappings where a USER exists in both the Company and User Group?
Thanks,