SMSc3.5: User is able to pass null custom urls through request

Project: SMSc3.5
Test Env: yell-dev-mms1

Description:
When null custom parameters are passed using deployCampaign request of adMaxServiceBinding, the custom urls in SMSc are also shown as null. This must not be the case, on passing null
parameters in request, SMSc must display default values.

Steps:
1. Run deployCampaign request of adMaxServiceBinding to create a new campaign.

• Use null values for newly added "displayURL" and "destinationURL" parameters in request
  2. Deployed a site using deployCampaign request of siteGeneration for same BpId
• checked that the site has been created
  3. Log into SMSc3.5 using valid credentials
  4. Navigate to "Google Adwords Campaign Settings" tab and observe "Google Adwords Click URL"

Observation:
The custom urls in "Google Adwords Campaign Settings" tab of SMSc are shown as null. Using the SMSc GUI, a user is not allowed to set destination url and display url as null.
Probably we can apply the same rule when update is done through a request.

Note:
On clicking Default link, the values remain null and are set as default. (snapshot attached)