Parameter Override
With a parameter override, specific attributes of an input parameter can be overwritten or adapted for exactly one action descriptor.
| Attribute | Type | Description |
|---|---|---|
| Parm To Override * | Tool_Has_InputParameter | The input parameter of the referenced tool descriptor that should be adapted. |
| New Parm From [C] | Selection | Overwrites the “Parameter_From” attribute of the input parameter, see
Relationship: Tool Has Input Parameter for more information.
Possible values:
|
| New Static Value [C] | String
(multi line) |
Overwrites the "Static_Value" attribute of the input parameter, see Relationship: Tool Has Input Parameter for more information. |
| Remove Parm [C] | Boolean | Ignores these input parameters for this action descriptor. This is only possible if the input parameter is declared as optional,
see
Relationship: Tool Has Input Parameter for more information.
Default value is false |
The Parameter Override attribute mutually exclude each other. Only one attribute can therefore be interpreted. The "New Parm From" attribute, for example, only works if no static parameter ("New Static Value") has been set. Similarly, a parameter can only assume a static value if it should not be ignored ("Remove Parm").
Examples
The SCLM remote edit save action is an example of a parameter override of one of its tools. The parameter SCLM_PROP_PARM_FunctionCode which has a default value of 0 is overwritten in the Action_Has_Tool relationship to the tool SCLM_TOOL_ISPF_REX_CheckIn by the value 1. This parameter determines whether an element is only uploaded to the mainframe or also checked-in into SCLM. When the tool is used within a SCLM Check-in action the value of 0 is expected that means the element is check-in into SCLM. If it is used in a remote save scenario of the editor, the check-in into SCLM should not be done because the element still stays open in the editor. The check-in into SCLM is only done with the close action of the editor.
The action SCLM_ACT_ShowContainedMembersFiltered is an example for an action with parameter overrides of two of its tools. The result of the overrides is that the corresponding property values are taken from a preceding tool in the action instead of from the context as defined in the Tool _Has_Input_Parameter relationship.