t_BaseMessage_JSONMapping

format : stringFormat string to be used when formatting the value.For timestamp formats see the SimpleDateFormat Java class. For decimal, double, float, integer, and long formats see the DecimalFormat Java class. For boolean formats we use our own formatter that supports the following values. "Yes,True,#t;No,False,#f"Note: * the timezone from the current invocation context is used. * Decimal formatting symbols from the current locale are used   (e.g. period or space for thousands separator, etc.) * The format pattern is presumed to be a string id and is looked up in   the strings for the current invocation context. If not found, a second lookup   is attempted, prefixing the format pattern with "ids.format.". If that   also fails, then the format pattern is assumed to contain a format pattern   that can be passed directly to the format instance. Example "h:mm a" => "12:08 PM" "EEE, d MMM yyyy HH:mm:ss Z" => "Wed, 4 Jul 2001 12:08:56 -0700" "#,##0.0#;(#,##0.0#)" => "1,000.0"keyThe unique JSON object "key:value" combination to identify a message in a message table.Valid values based on“string”.[^:]+:.+name : stringThe name to use for this part in the JSON message. Defaults to the message part name.subtypeMessage and primitive subtype.For message subtypes, you may specify array or root. 1. Object subtype is the default and it begins with { and ends with }. 2. Array subtype which begins with [ and ends with ]. 3. Root subtype. There can be only one child message part of root. For value subtypes: 1. On timestamp type values, you may specify a subtype of date, time or datetime. 2. On binary type values, you may specify a subtype of base64 or hex.Valid values based on“string”. arrayrootdateTimedatetimebase64hex