Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: unspecified
-
Fix Version/s: None
-
Component/s: SMSc
-
Labels:None
-
Environment:
Operating System: Windows XP
Platform: PC
-
Bugzilla Id:3692
Description
Project: SMSc3.5
Test Env: yell-dev-mms1
Steps:
1. Run deployCampaign request of adMaxServiceBinding to create a new campaign (gptest16).
- Use custom display and destination URLs by using newly added "displayURL" and "destinationURL" parameters in request
2. Checked in content_editor_google database and observed that in keyword and adcopy tables, the entries contain custom urls used in step1.
3. Now deployed a site using deployCampaign request of siteGeneration for same BpId - checked that the site has been created
4. Log into SMSc3.5 using valid credentials and observe the custom urls
Observation:
Observed that the custom urls in SMS3.5 are set as default when user logs in the verify first time. One would expect the custom URLs to not be marked
default and hence on clicking the default link (which is disabled at present) the custom URLS must be replaced by default ones.
Attached snapshot of Custom URLs marked as default.