Define a Template Gen Config file for a LOB from a generated file
You can generate a Template Gen Config file for line of business (LOB) and then use the generated file to complete the configuration based on your requirements. As part of the Cloud Retrofit with the APD App and APD Conversion (EA), you can use the Template Gen Config file (template_gen_config.lob_prefix.yaml) to change default values and define configuration details that can't be automatically inferred from the data model when generating the REST APIs.
About this task
When PolicyCenter generates the template configuration file for a LOB, it creates a
template_gen_config.lob_prefix.yaml
file in the config/apd/model/generate/json/ folder. Then, it
adds the following content to the file based on the LOB configuration:
- If a type is not configured as a coverable, exposure, or location or marked
as
ignored, it is added with a default ofexposurehandling and aTODOcomment indicating that the handling must be set, or that the type must be marked asignored. - If a field has an illegal name, the
fieldNameconfiguration is added and defaulted to the field's current name appended with the_1suffix. ATODOcomment indicates that it must be renamed. - If a field has a type APD cannot map, the field is added with the
ignored: trueflag and aTODOcomment explaining why it is excluded. - If autonumber sequences are unassigned, no configuration is added but a
TODOcomment is added to the containing type that explains which sequences are not handled and must be added to the appropriate children. - If there are multiple arrays of Coverables, PolicyConditions, or Exclusions
on a Coverable, the
coveragesArray,conditionsArray, orexlcusionsArrayproperty is added with a default value, along with aTODOcomment that indicates that the value must be set appropriately and lists the possible options.