How about adding a check box on forward engineering to add standard audit columns to all tables being engineered?
We can do it today using the table template transformation but that is a manual step you have to execute after forward engineering new entities. (works well but a bit annoying to do over and over again in an iterative design approach)
So you could basically just add the option to automatically use a template table and the current script. You might also deliver a default template table that the user can modify perhaps (then they can apply their own naming standards to the columns).
Your request will be a nice to have, I had the same need and used the table template transformation approach.
How about allow to define Scripts in entity properties for logical model (as already exists in the table properties for relational model) that is applied when being engineering to relational. This allows to define different "templates" to apply according each entity (audit columns in transactional entities, versioning/history columns in content entities, etc. ).
I use similar approach in the relational to DDL step using the table scripts (before create, after create,etc.) .
Because we use an internal data dictionary framework, each table that is added need to be categorized before to be possible to create the object.
So, this feature allow me to add in each table properties a Script "Before Creation" where an anonymous PL/SQL block is used invoke the method with classification and set this script to "Include into DDL script".Making the use of "dynamic properties", we dynamically define certain properties of categorization that will be used in the creation of script.
So I think that the enhancement of scripts in entities + dynamic Properties (already existing) will be a interesting mix for DM empowerment.