Adding fields to OLC events

Nicholas Marsh

What are the steps to adding a new field to OLC events, so that they can be referenced within transformers?

Nicholas Marsh

-In BillingConversionSpringConfig.xml, all transformers of the types which were to be modified were identified. These were mapped to logic dependent conversions, which existed in conversion list beans. Those conversion lists were mapped to Billing Condition Templates.
-The billing condition templates identified were located in BillingConditionSpringConfig.xml. These templates mapped Rest and Page cobalt events, and these were identified.

-All Page and Rest events identified had the PERMISSIBLE_USE entry added to their Extraction Maps.

**GOTCHA**: However, this alone broke the CrazyTrain integration tests, as not all such events would have PermissibleUse valued. So, permissibleUse was also added to the optionalExtractionKeys table within each appropriate Rest or Page event bean definition. In general, new fields added to Cobalt Events should also be added to the OptionalExtractionKeys list, as they are unlikely to be valued on every event of that type that is generated.

-When the field has been added to the extraction maps, it will be available from the releventEventBillingData supplied to the transformers.