New object creation records whether a system can be given an entirely new type of record, not just a new field on an existing one. Most systems allow custom fields; far fewer allow a new entity with its own records, relationships and permissions. Four routes are recorded, based on established practice rather than theoretical possibility.
- No code: new record types are created directly through the system’s own administrative interface, with no code to write and no build step. An administrator without a development background can define a new entity and put it into use without vendor involvement.
- Low code: extending the data model requires some technical skill, such as writing SQL or working in a low-code configuration layer, but stops short of a full development cycle. This usually falls to an IT-literate staff member, a consultant, or the vendor.
- Developer or vendor: a route exists and is regularly used, but requires writing, packaging and deploying installable code. The work may be done in-house, though it is more often bought from the vendor or an implementation partner as an ongoing service.
- None identified: no established or regularly used route to creating new record types was found. This covers both fixed-model products, deliberately not designed to be extended, and products that may be extensible in theory but without documented practice.