Stringified Value Format: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
QPR ProcessAnalyzer uses the '''stringified value format''' in several places when [[Filtering_in_QPR_ProcessAnalyzer_Queries|filters]] are defined using the JSON format. The stringified format encodes data of different types into a string format (which is supported by JSON format).
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 first character in the stringified format represent the type of the data. The conversion is needed because JSON only supports strings, numbers and booleans.


The stringification is done according to following rules:
The stringification is done for each data type according to following rules:
{| class="wikitable"
{| class="wikitable"
!'''Data type'''
!'''Data type'''
! '''Prefix'''
! '''Format'''
! '''Format'''
! '''Example'''
! '''Example'''
|-
|-
||string
||string
||0
||0<string value>
||0<string value>
||
||
* Patricia White -> 0Patricia White
* Patricia White -> 0Patricia White
* 321 -> 0321
* (empty string) -> 0
|-
|-
||decimal number
||decimal number (float)
||1
||1<decimal value>
||
||
||
* 74.435 -> 174.435
* 0.1 -> 10.1
* 0.0 -> 10.0
* -1.456 -> 0-1.456
|-
|-
||date
||date
||2
||2yyyy-MM-ddTHH:mm:ss.fff
||2yyyy-MM-ddTHH:mm:ss.fff
||
||
* 1st of July 2018 -> 22018-07-01T00:00:00.000
* 12th of October 2021 at 08:34 -> 22021-10-12T08:34:00.000
|-
|-
||null value
||null value
||3
||3
||3 (means null value)
||
||
|-
|-
||Small integer
||small integer (maximum allowed value 2 147 483 647)
||4
||4<number value>
||
||
||
* 1234 -> 41234
* -300 -> 4-300
|-
|-
||Large integer
||large integer
||5
||5<number value>
||
||
||
* 3000000000 -> 53000000000
* -12345678900 -> 5-12345678900
|-
|-
||boolean
||boolean
||6
||6True or 6False
||6True or 6False
||
||
|-
|-
||timespan
||timespan (duration)
||7
||7d.HH:mm:ss.fff
||7d.HH:mm:ss.fff
||
||
Line 51: Line 54:
* 6 hours -> 70.06:00:00.000
* 6 hours -> 70.06:00:00.000
* 1.3 seconds -> 70.00:00:01.300
* 1.3 seconds -> 70.00:00:01.300
* -43 minutes -> 7-0.00:43:00.000
|}
|}
[[Category: QPR ProcessAnalyzer]]

Latest revision as of 10:25, 2 November 2022

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 first character in the stringified format represent the type 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>
  • Patricia White -> 0Patricia White
  • 321 -> 0321
  • (empty string) -> 0
decimal number (float) 1<decimal value>
  • 74.435 -> 174.435
  • 0.1 -> 10.1
  • 0.0 -> 10.0
  • -1.456 -> 0-1.456
date 2yyyy-MM-ddTHH:mm:ss.fff
  • 1st of July 2018 -> 22018-07-01T00:00:00.000
  • 12th of October 2021 at 08:34 -> 22021-10-12T08:34:00.000
null value 3
small integer (maximum allowed value 2 147 483 647) 4<number value>
  • 1234 -> 41234
  • -300 -> 4-300
large integer 5<number value>
  • 3000000000 -> 53000000000
  • -12345678900 -> 5-12345678900
boolean 6True or 6False
timespan (duration) 7d.HH:mm:ss.fff
  • 2 days -> 72.00:00:00.000
  • 6 hours -> 70.06:00:00.000
  • 1.3 seconds -> 70.00:00:01.300
  • -43 minutes -> 7-0.00:43:00.000
Retrieved from "https://wiki.onqpr.com/pa/index.php?title=Stringified_Value_Format&oldid=21932"