Groovy scripts can be added as transformers in the transformer.json configuration. RIF-CS can be inserted, in no particular order, alongside say local and jsonVelocity, like so:
In the above example, the RIF-CS configuration has:
The example also shows that the jsonVelocity configuration has a field:
When choosing to run the RIF-CS script transformer instead of the RIF-CS velocity template, this configuration must be included. Otherwise both the rifcs transformer and the velocity template will run, with the results of the velocity template overwriting the groovy script.
(If the choice is to run the rif.vm template instead of the RIF-CS groovy script, then leave this field out or set its value to empty square brackets, as well as removing the RIF-CS 'scripting' configuration).
Of course, any of the json velocity templates which run as part of the json velocity transformer library, can be added here - in comma-delimited format - in order to be excluded.
When performing a redbox upgrade and running the tf_restore.sh script, if you are planning to also allow the RIF-CS transformation to run, then you must also enable harvest remapping in migration.json.
In the example, above, enabled is set to true, enabling the RIF-CS logic to run as part of harvest remapping.