We've created a notification endpoint that we send data to. Part of the data is a userID that potentially contains leading zeros. So a valid user ID could be "010201". This value comes from a configuration attribute that is configured as a string. When we test the subscription, the JSON that is generated sends an integer value that strips off the leading zero. So "010201" comes through to the endpoint as "10201".
I was hoping that setting the configuration item to a string type would maintain it, but that didn't work.
Is there any way to maintain that leading zero?
User ID Configuration Attribute:
"User ID": 10201