Account coding parameters — table, validation, rights
The key–value parameter table of the type adapters, value type checks, uniqueness, deletion and the permission keys.
The coding parameters of the type adapters (for example mol, idata, merkantil, otpkelfo) as key–value pairs. The adapters receive them through getConfigArray().
Data model
Table names carry the installation's own prefix in the database.
| Table | Main fields |
|---|---|
contir_config | type, group, key, value (config_value), value type (string, int, json), status, note |
Deleting a ledger account looks for references in the config_value field (see the chart of accounts article).
Save and delete
- Type and key are required (
error_type,error_key). - For
jsonvalid JSON after decoding HTML entities (error_json); forintan integer (error_int). - Type + group + key unique (
keyExists,error_duplicate); save withsaveConfig(). - Delete: physical (
deleteConfig), without a reference check. - Status:
finance/contirconfig.status.
Permissions
| Key | Use |
|---|---|
list (UNMAPPED) | in getList(); index() loads the types without a right check |
add | not in the seeds; the button is hidden for non-super-admins, canSave(0) falls back to edit |
edit | form and status: canAction(edit); save: canSave |
delete | canAction(delete) |
statusdelete | BASE, seed only; there is no status-9 endpoint |
debug | filter SQL toggle |