We want to control permission for Pin/Ignore of attributes for specific attributes.
The permission does not have to be user based, though it can be -- but needs to be granular.
For example:
a) Allow only for specific attributes or conversely prevent only for specific attributes
b) Permit only for simple attributes
c) Permit for nested attributes but only at the nest level and not for individual attributes
There are 2 reasons that this would be helpful:
1) We are seeing that Hub permits a sub-attribute of a nest to be pinned, but it actually is not having impact on the nest.
This behavior actually makes sense, since you don't want sub-attributes out of alignment, but yet the Hub permits it
2) We are deactivating non winner crosswalks and as such when doing so the OV attribute is becoming null even when there are other active crosswalks with some different value for the same attribute. As a work-around we will be updating and pinning values to a different crosswalk before the deactivate.
We want to prevent where we are using aggregation survivorship due to the complexity and expense of "chasing it down".
Thanks,
Mark
------------------------------
Mark Burlock
Dodge Data & Analytics
Hamilton NJ
------------------------------