UMI API data types

The api is multiplatform and so are its data types.

name type
<int> integer signed value of 32 bits
<long> integer signed value of 64 bits
<string> a string
<boolean> a boolean
<decimal_string> decimal value (like float number but of higher precision)
<timestamp> date and time in  ISO 8601: Extended Format
<simple_type> any on above listed types
<remote_object> a structure represending remote object created on UMI tool side { __type: RemoteObject, id: <long>, className: <string> }
<remote_object_no_type> a structure represending remote object created on UMI tool side { __type: RemoteObject, id: <long>, className: <opt_string> }
<serialized_object> a structure represending complex datatype in the serialized form { __type: <string>, ... }
<invoсation_result> is either <simple_type> or <serialized_object> or <remote_object>
<invoсation_param> is either <simple_type> or <serialized_object> or <remote_object_no_type>

If the type is prepended with opt_ prefix, e.g. <opt_string>, it means that corresponding parameter may be omitted or missing.

If the type is prepended with vararg_ prefix, e.g. <vararg_string>, it means that there could be 0 or more parameters of corresponding type.