Multilingual Customization and Resource Structurehttps://coderlegion.com/35102/day-20-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...
A system sold into several regions needs its field captions, form names and dropdown option text to change with the language. Anyone who has done internationalization has handled this, and .NET's standard answer is .resx: strings go into a resource f...
An ERP installed and used as it comes is close to nonexistent. The same set of definitions goes out to three companies, and one of them wants "customer" to read "dealer", the second wants three fewer fields on the order screen, and the third wants on...
A failed call comes in two kinds. One is a business rule stopping something in the normal course of things, an order with no customer selected, a status that cannot move that way, and that message is written for the user. The other is an exception th...
The previous post, JSON-RPC 2.0: Protocol Choice and the Request Pipelinehttps://coderlegion.com/34683/day-16-json-rpc-2-0-protocol-choice-and-the-request-pipeline, was about how a call is handled once it reaches the server. The same contract needs s...
The previous post, API Contract Layering and the Type Registryhttps://coderlegion.com/34577/day-15-api-contract-layering-and-the-type-registry, was about how the framework knows which type to build once a call arrives. The question one step earlier i...
The extension points from the previous post, Extension Points on a Business Object and When to Override Themhttps://coderlegion.com/34413/day-14-extension-points-on-a-business-object-and-when-to-override-them, all hang on one concrete business object...
Behavior a definition can express needs no code written at all. The ones it cannot express are what needs taking over: what to check before this document is submitted, who to notify after it is saved, and under what circumstances a delete is not allo...
Every request in an ERP system has to answer two things first: who is calling, and which company they are in. Without the framework managing that centrally, those two questions grow into the opening of every stretch of business logic, as boilerplate ...
Opening one form means the framework reads more than one definition: FormSchema, TableSchema, FormLayout, ProgramSettings and LanguageResource, none of them optional. These definitions still change after go live, but they change rarely while the syst...
How FormSchema Drives SQLhttps://coderlegion.com/33442/day-5-how-formschema-drives-sql drew the boundary of the definition-driven route: relationships across tables are always single column equality, and what they join to is always a physical table. ...
"Supports SQL Server, PostgreSQL, MySQL, Oracle and SQLite" is one line in a specification. Inside a framework it is a question that has to be answered before anything else: what exactly is being abstracted for them.
Neither direction works:
Wrappi...
One request travels front end, API, business object, repository, database, and every layer has to receive the same record. What most systems put here are types they wrote themselves: an Entity per table, a DTO on each side, and a layer of Mapper conf...
What the last few posts grew out of definitions were concrete products: tables, CRUD statements, screens on four front ends. Today's item builds nothing. It takes the expressions written into the definition and evaluates them, either writing the resu...
TableSchema and Database Structure Upgradeshttps://coderlegion.com/33644/day-6-tableschema-and-database-structure-upgrades ended at physical tables, where one change means moving data and working out beforehand whether you need downtime. Today is bac...
Yesterday's SQL was all about accessing data. Today is about something else: where those tables came from in the first place.
Which columns a table has, how long each one is, and which ones get an index, are authoritative in TableSchema. The physica...
The previous post, The Purpose and Classification of Definition Fileshttps://coderlegion.com/33352/day-4-the-purpose-and-classification-of-definition-files, laid the definition files out one by one, and FormSchema is the hub among them. Today, a conc...
"Definitions are the single source of truth" sounds like there is one file holding all of the truth. Open a project's definition directory and what you actually see is thirteen definition types. Some are a single file at the root, and some are one fi...
The first two posts were about the argument. Today the case study comes on stage.
The case study is Northwind, Microsoft's sample database that has been passed down since the Access era. The reason for choosing it is practical: customers, suppliers,...
The previous post, Why ERP Needs a Definition-Driven Frameworkhttps://coderlegion.com/33030/day-1-why-erp-needs-a-definition-driven-framework, ended by promising this one would be about which decisions a framework should make on its users' behalf.
T...