This is the safest way to write scripts that affect multiple data tables and/or records. Karbon transactions also makes it simple to cache data for performance reasons, and validate business rules.
Much of the code we write are repetitions of common patterns (e.g., parameter validation, initializing parameters). We can generate code based on a library of common patterns and existing database schema; this produces higher quality and more consistent code, and saves a ton of time in the process.
Karbon both embraces modules and has created its own modules that can be reused from project to project. Why reinvent the wheel for other projects that aren’t based on Karbon?
Our scripts in the kontroller file are designed to expose Create, Read, Update and Delete (CRUD) functionality in a consistent, testable fashion to FileMaker clients and external applications.
Our testing module allows us to validate that our script APIs are functioning based on a series of unit tests
Karbon uses industry standard data modeling techniques to create a data model that is both flexible and robust. The contact management system is an implementation of the Party Model
The Inbox feature of Karbon Connector handles inbound data flows from other systems. Data lands here first before being processed into the system.
Based on jsDocs, Karbons documentation standard is readable by human and machine, making it well suited to developer tools like Generator and FMPerception