Allow empty field handling in integrations

If you work with custom integrations a lot this improvement might help you quite a bit.

When dealing with third-party software and their API's they tend to handle empty values differently. With this new setting, you can determine how this integration will send empty fields to the third-party software.

The options are the following:

"Send empty string as empty ("")" which will

• This will send the empty string as an empty string e.g. "fieldName": "".

Send empty strings as null

• Will send all empty fields as the value "null"

Skip empty fields in requests

• This functionality will not send the empty fields at all, so skip it out of the request entirely

You can find this configurations under the "Settings" section inside your integration.

Why did we implement this improvement?

• More control of Integration requests
• Regularly requested, indirectly or directly by users