Hi Govardan,
a track has a server side development config (created as per the domain data settings and track data settings i.e. includes cbs, dtr, cms url, sld nameserver and the software component dependencies).
It is an XML file you can check in CMS webui -- Track Data -- Build variants -- display development config.
If you create a devconfig in your NWDS, then this XML file is getting synced to your local space (this is the file called .confdef).
After this no more sync is getting done, but the locally stored .confdef is used by the devconfig, so it knows, which cms, dtr, cbs , sld to contact, etc. in other words: how to use the track.
If you change on the server side devconfig (by changing on say cbs, dtr or sld url or SC dependency setup) then NWDS recognizes that its locally stored .confdef became outdated.
This is why you have that popup that the server side devconf version XY is now available and you can make the locally stored one up to date.
I hope this answers your question.
Best Regards,
Ervin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.