Customizing Configuration Settings

The core component contains a copy of the curam-config.xml file, but you are free to augment and override the settings by including your own curam-config.xml file in your custom component. All of the individual curam-config.xml files will be merged into one at generation. The effect of this merging depends on each particular setting.

Some entries are global settings for the application and so must only appear once in the final output. These entries are as follows:

If you define one of these in a custom component, it will completely override that of the core component.

The other entries will be merged. This applies to the following elements:

Note, however, that particular address formats can be overridden. So, for example, if the core component had the following address format definition:

Figure 1. Extract from curam-config.xml File (1)
<ADDRESS_FORMAT NAME="US" COUNTRY_CODE="US">
   <ADDRESS_ELEMENT NAME="ADD1"
                    LABEL="Core.Label.Address.1"
                    MANDATORY="true"/>
   <ADDRESS_ELEMENT NAME="ADD2"
                    LABEL="Core.Label.Address.2" />
   <ADDRESS_ELEMENT NAME="CITY"
                    LABEL="Core.Label.City" />
   <ADDRESS_ELEMENT NAME="STATE"
                    LABEL="Core.Label.State"
                    CODETABLE="AddressState"
                    MANDATORY="true"/>
   <ADDRESS_ELEMENT NAME="ZIP"
                    LABEL="Core.Label.Zip" />
</ADDRESS_FORMAT>

and if your custom component had the following address format definition:

Figure 2. Extract from curam-config.xml File (2)
<ADDRESS_FORMAT NAME="US" COUNTRY_CODE="US">
   <ADDRESS_ELEMENT NAME="ADD1"
                    LABEL="Custom.Label.Address.1"
                    MANDATORY="true"/>
   <ADDRESS_ELEMENT NAME="ADD2"
                    LABEL="Custom.Label.Address.2" />
   <ADDRESS_ELEMENT NAME="CITY"
                    LABEL="Custom.Label.City" />
   <ADDRESS_ELEMENT NAME="STATE"
                    LABEL="Custom.Label.State"
                    CODETABLE="AddressState"
                    MANDATORY="true"/>
   <ADDRESS_ELEMENT NAME="ZIP"
                    LABEL="Custom.Label.Zip" />
</ADDRESS_FORMAT>

then it is the second one (i.e., the custom definition) that will appear in the final merged curam-config.xml file. This is because both address formats have the same name ("US").