When to Override a Business Object's Extension Points in a Definition-Driven Framework

This Day 14 post explains when a developer should inherit from a business object instead of relying on declarative definitions. It describes how a save operation is split into several steps, with the framework dictating the order of overridable hooks. The author sorts customizations into three levels, from declarative expressions to plugins to inheritance, with inheritance reserved as the last resort. The guidance is that logic common to all organizations should be collected into framework mechanisms, while organization-specific rules legitimately justify inheritance. An example of a packaged leave request shows how a product form and a customer-specific variant can each override validation at different levels.