Overriding Configuration
Configuration and NLS can be modified by adding a config.jsonc file in the $HOME/flex folder containing JSON data mirroring the folder structure in the product configuration/NLS files and the structure of the JavaScript objects defined in those files. Any Flex configuration can be modified in config.jsonc, but it is recommended to instead override individual configuration files, for example, the Work Agenda tool configuration files can be overridden by adding overrides in
$HOME/flex/client/tools/workAgenda.jsonc
The comment at the top of the product configuration file indicates the files where the configuration can be overridden:
/**
* You can modify these configuration options by adding overrides to either the
* main config/config.jsonc file or config/client/tools/workAgenda.jsonc
*/
If there is not comment like the one above, then it must be overridden in the main config.jsonc file.
Note: All NLS must be overridden in config.jsonc
Example configuration tasks and the exampleCustomConfig.jsonc file provided with the distribution (in the dist/baseconfig/product/flex/examples folder) shows how to override some specific configuration. The exact method used to override depends on the type of data being overridden in the JavaScript configuration file, which will be described in more detail in the following sections.