Param
Parameters are used to pass values to commands.
| XML | |
|---|---|
Attributes
Required:
name
Optional:
label- nametitle- placeholderscope- command - parameter will be applied only to 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 defaulttextselect- dropdown typenumberintegermoneydecimal/ decimalintbiginttinyintsmallintinteger/ bigintuniqueidentifieruuid/ uniqueidentifierdate/ datedatetimedatetime2smalldatetimetime/ datetimefloat/ floatxml/ xmlansi/ varchartext, password, hidden, color, checkbox/ nvarchar-
- you can use any type https://www.w3schools.com/tags/att_input_type.asp
optsserver- server side parameter useful for predefined values cannot be overwritten by userjson-xml- convert json to xmljson-xml-root- convert json to xml (root element created, if array of items each item wrapped in row)json-xml-body,json-body- special, body request as parameterreq- parameter required
Notes
Using proper data type is important for proper data validation
Parameters Processing order
Parameters are processed in the following order:
- Server side parameters (cannot be overwritten by user)
- Query String
- Body Parameters
- SQL injections Using parameters is safe and recommended. To better understand what is SQL injection and why we do not allow processing commands read https://owasp.org/www-community/attacks/SQL_Injection
| XML | |
|---|---|
Examples
Parameter UI
| XML | |
|---|---|