Custom Batch Control Validation

The extensible / custom batch control files need to follow the guidelines previously to futureproof the retailer. That means the retailer should receive software updates without breaking the existing customizations. To ensure that the batch control file guidelines are adhered to, a batch control validation module has been added.

The ra_config_validation.sh script has an optional parameter -b <parent directory of batch control files> which will validate the batch control files.

Batch control validation rules:

• Apart from batch_oat_list.txt, none of the set names in the other batch control files can be overridden. That is, GA set names cannot be used in custom batch control files.

• None of the custom batch control files can call the GA set names.

• The batch_calc_list.txt file can only specify custom rule group names. Cannot specify expressions and GA rule group names.

• The batch_loadmeas.txt_list file can specify measures that are listed in the Loadable or Writable list of the published measures in the published<app>Measures.properties file

• The batch_exportmeas_list.txt file can specify measures that are listed in the ReadOnly or Writable list of the published measures in the published<app>Measures.properties file.

• All custom set names should have a prefix of c_.

Note:

The batch control validation is called automatically during domain build or patch. It is also called when the batch control files are uploaded using the Upload Batch Control files from OAT.