Param
Parameters are used to pass values to commands.
| XML | |
|---|---|
Attributes
Required:
name
Optional:
label- display nametitle- placeholder textscope- parameter will be applied only to the matching command (comma-separated values available)textnull- equals null- server-side variables
[[variable]]are available; see server-side variables
lg- hide/show on desktopsm- hide/show on mobiletype- UI type / DB type, default istextselect- dropdown typenumberintegermoneydecimal/ decimalintbiginttinyintsmallintinteger/ bigintuniqueidentifieruuid/ uniqueidentifierdate/ datedatetimedatetime2smalldatetimetime/ datetimefloat/ floatxml/ xmlansi/ varchartextpasswordhiddencolorcheckbox/ nvarchar- you can use any input type; see https://www.w3schools.com/tags/att_input_type.asp
optsserver- server-side parameter; useful for predefined values that cannot be overwritten by the userjson-xml-root- takes the property and converts it to XML; supports for arrays, array is forced and elements are wrapped in a rowjson-xml- takes the property and converts it to XML; will throw an error if the JSON is an array; usejson-xml-rootfor arrays or send JSON with a root elementbody-xml-root- takes the body as is and converts it to XML; supports for arrays, array is forced and elements are wrapped in a rowbody-json- takes the entire body as JSON and sends it as JSON; supports JSON objects and arraysreq- parameter is required
Note
Deprecated aliases: json-xml-body → body-xml-root, json-body → body-json.
Note
Using the correct data type is important for proper data validation.
Parameter Processing Order
Parameters are processed in the following order:
- Server-side parameters (cannot be overwritten by the user)
- Query string
- Body parameters
Using parameters is safe from SQL injection and is recommended. To learn more, see OWASP SQL Injection.
| XML | |
|---|---|
Examples
Parameter UI
| XML | |
|---|---|