Custom action processors cater to a specific purpose that is outside the scope of the cartridge action processors.
When working with custom action processors, see the following topics:
Solution designers can create custom action processors to perform actions outside of the scope of the action processor in the cartridge. For example, a custom action processor may be necessary when a certain piece of data is required by a subsequent atomic action but is not provided by the upstream system. Generally a custom action processor will produce but not consume data. It simply generates data for use in subsequent spawning logic, for use in the generation of an API/MML command, or to query the switch for a piece of data that is to be passed back to upstream systems. Custom action processors generally do not talk to the network element but do some special processing of data, such as running a special algorithm to encrypt a piece of data or performing special formatting of data that may not have been handled by the upstream system or by the cartridge action processor.
To create a custom action processor:
Create a new atomic action that will trigger 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 will involve some type 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
Understanding the Java Processor Class