UpcaseDataItemValue default causing backwards compatability issue

[neildes2]

The default value for this new parameter should be false to be backwards compatible. One would think that 'true' is inline with the standard, however there is a use case that shows it should be false.

UseCase:

Extended TYPE with a json payload for a value. The payload is set to all upper case and breaks parsing the object.

from README

UpcaseDataItemValue - Always converts the value of the data items to upper case.

Default: true

[wsobel]

I can change the default value for this transform. I check historically and it was true going back quite a few versions. I need to check when we changed it to true.

[wsobel]

I checked back to version 1.3 and it was always defaulted to true. (Tag v1.3.0.0).

The behavior can be changed at the top level to flow to all the adapters. I'm hesitant to change this behavior since it may break other assumptions in other installations.

[wsobel]

Need to validate which pipeline is being used and if there were any changes between 2.4. and 2.5. If different behavior, we need to understand when it was introduced.

[wsobel]

Do you have the configurations for 2.4/2.5 and the device xml with the agent.cfg? I'd need more info to reproduce