Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Dealing with empty strings vs null in JSON to XML to JSON conversions

in Process Automation 2 comments

Summary:

How to deal with process cloud doing the JSON-->XML-->JSON conversions, where the first JSON message contains an empty string ("") but after two translations, this turns into null when doing the REST call.

Content (please ensure you mask any confidential information):

Hi,

We're currently working on a process application where the following happens:

1. Process is designed with a message start event, that contains an optional parameter "myOptionalAttribute".

2. Process is started from a VBCS web app with a payload containing "myOptionalAttribute" : "" (JSON representation of empty string), if myOptionalAttribute has no value.

3. Process cloud starts a process instance and automatically it translates the received empty string for myOptionalAttribute to the XML representation <myOptionalAtttibute/>

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!