You can create custom action processors to perform actions outside of the scope of the action processor in the cartridge project. For example, a custom action processor may be necessary when data is required by a subsequent atomic action but is not provided by the upstream system. Generally, a custom action processor produces but does not consume data. Customer action processors generate data for use in subsequent spawning logic, for use in the generation of an API/MML command, or to query the switch for data required by upstream systems. Custom action processors typically do not communicate with network elements. Rather, they process data. For example, you might create a custom action processor to run an algorithm that encrypts data or that performs formatting of data that may not have been handled by the upstream system or by the cartridge action processor.
See "Creating Custom Action Processors" for more information.
To create a custom action processor:
Create a new atomic action that triggers the custom action processor.
Include the parameters required for the atomic action.
Create a new action processor and link it to the new atomic action.
Creating a new action processor involves some level of coding (either a state table or Java processor with code generation method).
Link the new atomic action into your service model wherever it is needed.
Working with Custom Action Processors
Creating Service Actions, Atomic Actions, and Action Processors