All available enumeration types in the CTT settings are currently hard-coded in the binary, which requires a new binary update and a new setting type for each new enumeration to be available in the settings (e.g. ValueType_MessageSecurityMode, ValueType_PkiType or ValueType_SecurityPolicy).
By implementing a new header column for type meta-data in the default.ctt.xml file along with a new ValueType_Enumeration setting type using this data to obtain the needed enum fields (by providing the name of the enum already available in the CTT), new enumeration settings could be implemented directly in the default.ctt.xml file, without hard-coding the type each time.
Furthermore, a setting type for JSON-encoded enumeration data, which will then be defined in the new TypeMetaData field, could be used to define custom enumeration types as well.