Multilingual Customization and Resource Structure ended on a situation where the difference one company wants is too large for language resources or layouts to hold. Requests of that kind have a different shape from the two posts before: one more credit limit check before a save, a document synchronized to another system after a save, a notice to the warehouse on a delete. What they want is not a definition that reads differently, it is a piece of behavior that runs.
The framework already has a route for that: inherit the whole form's business object and swap the binding in the registry. But that route is too heavy for the three things above. Sending one notification after a save means taking over the business object for the entire document. Three unrelated customizations stacked together can only be written into the same subclass. And whether logic the package adds to that step later still runs at all depends on whether the subclass remembered to call base .β¦