Stringified Value Format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
QPR ProcessAnalyzer uses the '''stringified value format''' in [[Filtering_in_QPR_ProcessAnalyzer_Queries|filters]] when | QPR ProcessAnalyzer uses the '''stringified value format''' in [[Filtering_in_QPR_ProcessAnalyzer_Queries|filters]] and [[Web_API:_Expression/query|expression queries]] when values are defined in the JSON format. The stringified format encodes different types of data into a string format that captures both the type and value of the data. The conversion is needed because JSON only supports strings, numbers and booleans. | ||
The stringification is done for each data type according to following rules: | The stringification is done for each data type according to following rules: |
Revision as of 16:55, 26 January 2021
QPR ProcessAnalyzer uses the stringified value format in filters and expression queries when values are defined in the JSON format. The stringified format encodes different types of data into a string format that captures both the type and value of the data. The conversion is needed because JSON only supports strings, numbers and booleans.
The stringification is done for each data type according to following rules:
Data type | Format | Example |
---|---|---|
string | 0<string value> |
|
decimal number | 1<decimal value> |
|
date | 2yyyy-MM-ddTHH:mm:ss.fff |
|
null value | 3 | |
small integer (at maximum 2 147 483 647) | 4<number value> |
|
large integer | 5<number value> |
|
boolean | 6True or 6False | |
timespan | 7d.HH:mm:ss.fff |
|