You can use an XML definition instead of JSON to define your custom steps. The file must be named
steptypes.xml and placed in a custom cartridge in the root folder. The XML file is parsed and reloaded whenever the active code version is changed. You can only have one
steptypes.xml file per cartridge.