Use cases to be covered:
Whether or not the value of the attribute associated to the class is carried over to a new instance
Whether or not to completely remove the association to the (legacy) attribute not associated to the class when creating a new instance
Notes:
For (1), it should be possible to define the class attributes behaviour for each attribute individually at a parent class level and inherit down the class hierarchy.
For (2), a setting on the (parent) class should be sufficient and will apply to all legacy attributes on the class instance. By default, the setting must be inherited down the class hierarchy.
At minimum, this should be supported for documents.
The same settings will be applied equally to both CC and non-CC objects.
The same settings will be applied equally to both revising or copying objects.
It should be possible to set the above behaviour via the import/export tool.
|
What underlying problem is this idea trying to solve?
Currently the only way to address this is via configuring automations / event handlers. And automations do not support multivalued attributes for this case. |