Apama measurements should support integer value similar to Cumulocity API

If Cumulocity API allows floats and integers for measurement values then Cumulocity Apama should support integers also.

Float is problematic when Cumulocity user expects integer values but get floats. 0 and 1 can represent false and true. 0.0 and 1.0 is confusing as Boolean representation.

It seems strange that built in real time processing has less options that Cumulocity API when creating measurements.

Cumulocity API allows integer https://cumulocity.com/api/10.11.0/#operation/postMeasurementCollectionResource

"value - The value of the individual measurement. The maximum precision for floating point numbers is 64-bit IEEE 754. For integers it's a 64-bit two's complement integer."