Cached parameter tables
It's very useful to have parameter tables, keeping configuration and business rules outside of the code provides meaningful separation of concerns, whilst also affording adaptability. In EBX, it's common practice to create a parameters dataset where tables are created to configure the environment. There is a clear downside to this approach: EBX tables are slow to access and annoying to work with. This is where cached parameter tables come in. Cached parameter tables are nothing more than a parameter table with a cached access layer on top. The cache is initialized on repository startup using the module's register servlet and kept up to date during execution using a table trigger. Example As an example, let's build a cached parameter table for a keyd flags. This table must store key-value pairs, where the keys are strings that indicate which flag each row references and the values are booleans that indicate whether the flag is set or not. A...