cancel
Showing results for 
Search instead for 
Did you mean: 
Walter.Koller
Level 12
Status: New

Currently enable sharing on VBO exposes the application model of the base object to be used in other objects. Everything else is not available to the depending object and all actions need to be recreated.

It would be great to inherit everything so sharing also works with eg code based VBO and actions could be re-used (and maybe overridden with new action implementation). 

Example: We use assets from DX but over time we have to add new actions to the original VBO. After some time we would like to update the object with the most recent version from digitalexchange Importing the new DX object will remove all our new actions, so we have to first create a copy of our current object, import the new one object from DX and then selectively copy the our actions from temp object to newly imported object. 

import from DX: DX Asset v1 VBO
extend VBO: DX Asset v1 VBO (+new action)
copy VBO: DX Asset v1 VBO (+new action) > DX Asset v1 VBO (tmp)
import new DX: DX Asset v2 VBO (replacing DX Asset v1 VBO (+new action))
copy Actions: from DX Asset v1 VBO (tmp) > DX Asset v2 VBO (+new action) 

It would be much easier if we could create an object and inherit all actions from the base object and only add new action to the extension object. Replacing the base object won't need any additional efforts this way. 
Additionally it would be great to override base actions in the extension object to ensure consistent behavior. In case action logic in base object changed. This would also make maintenance easier in case we need to change base actions but don't want to have copies of same actions.
eg when we have to amend we have to either change the original action or duplicate the action

With override possible, we just have to add an action with the same name to the inheriting object.
This way we just have to open the inheriting object to see what was added and what was changed while not being affected by any newer object version from DX.