Action Processor Editor Request Tab

Use the Request tab in the Action Processor editor to define the parameters for a CLI command request messages. In the Command Definition Area area, you can define:

Separators: In this area, you can specify command parameter separators that override the CLI command structure you defined in the Action Project editor Command Structure tab.
Command: In this area, you can parse sample CLI commands and generate CLI code for the action processor.
Parameters: In this area, the elements are either automatically generated from the sample CLI command you parsed in the Commands area or you can manually add elements.

Field	Use
Overwrite	Select to override the default command structure defined in the Activation Project editor Command Structure tab. You must select this check box to make the separator fields editable. For more information about the fields in the Separators area, see the field definitions in "Activation Project Editor Cartridge Layout Tab".
Command Auto-Parse Override	Select if you want to automatically parse sample CLI input commands. This enables the Parse Input Command button.
Input Command	Enter a sample CLI command that represents the CLI command elements you want to use in the action processor.
Command Parameter	Click to designate the CLI parameter you entered in Input Command as a command parameter. If you designate a parameter as a Command Parameter, then you must choose the following: After you make your selection, the highlighted parameter appears in the Element Name list. When you select one of the auto-generated parameters from the Element Name list, the associated atomic action parameters appear in the Maps To field (except for StaticString parameters).
Command Header	Specifies the command header. You can: Manually enter the command header in this field. Highlight a command header in the sample input command you entered in the Input Command field and select Command Header. Click Parse Input Command to have the action processor automatically enter the command header based on the command structure.
Parse Input Command	Click to automatically Parse Input Command button after you have entered a sample CLI command that you want to tokenize.
Element Name	Lists the parameters that you want to use in the action processor. You can automatically generate these parameters by parsing a sample command or manually add them.
Type	When you select an parameter from the Element Name list, you can apply one of the following parameter types from the Type list. Name Value Pair: When you select this option, the element name and value are used. You must select a parameter from the atomic action from which the value is populated. ValueOnly: When you select this option, only the value is used. The element name does not appear in the command. You must select a parameter from the atomic action from which the value is populated. StaticString: When you select this option, the element name alone is used. Static strings do not contain values and may not be associated to atomic action parameters.
Maps To	When you designate parameters from the Element Name list as Name Value Pairs or ValueOnly, you must map the parameter to an atomic action parameter in the Maps To field. The action processor includes the value of the atomic action parameter in the request message.
Parameter Logic	In the Parameter Logic field, you can add one line logic for Name Value Pairs and ValueOnly parameters that further specifies how a atomic action parameter maps to a parameter in the Element Name list. This field calls the methods defined in the Utils.java file that Design Studio generates when you add a sample command to the Input Command field. All methods defined in Utils.java throw exceptions defined in the ProvCartridgeException.java file, which is auto-generated when you add a sample command. For more information about the methods contained in the Utils.java file, see ASAP Cartridge Development Guide. You can also nest two or more command together in the Parameter Logic field. For example the following uses the encloseWith method within the concat method: concat("*",encloseWith(MCLI,"#","#"),MY_TEST) Design Studio also generates the ReusableMethods.java file where you can define your own one line utility methods that you can use in the Parameter Logic field. The methods you define in this Java file should throw exceptions defined in the ProvCartridgeException.java file.
Edit Parameter Logic	Click to modify or add logic for a particular parameter. For example, if you have a parameter that maps to more than one compound parameter, you must enter additional logic. Clicking this button generates additional Java files where you can make these modifications. For more information about the files generated when you click the Edit Parameter Logic button, see ASAP Cartridge Development Guide.
Preview	Displays a preview of the structure of the CLI command as you map CLI command elements to atomic action parameters. For example, the following command shows a header named HSDPA, a value-only parameter, two value-pair parameters, two static parameters, and ends with the COMMIT control character: HSDPA:<mcliVal>,LCC_CODE=<user_routingVal>,LINE=<lineVal>,static, program,;COMMIT