this sounds familar to me, only because i wrote a vb.net gui which was driven by a custom xml file defining what controls to show to a user and what these controls should contain and whats more what should happen when the user selects different controls or enters data (in efftect it only pumped out properties which the user was assigning to a server or system being provisioned but thats not the point i guess)
to cut a long story short stavae, no one will have a clue as to how you can amend you xml to serve your purpose....unless you tell us which application you are using (in which case i am sure you will be directed to a different forum for that app, or you will be asked to read the manual), but, if that application was written by you and you have the source code, then depending on the source code type you will again be directed to a different forum.
i hope that is ok?
p.s. the users of the gui i wrote then started asking me to do stuff with each of the controls so that each controls behavour depended on each other and the users selections, i scratched my head and told them no, i had exhausted the benefit of the data driven gui and would be better to write the interaction in native / normal vb.net control manipulation thing. saying all that perhaps MS's appplication XML which is rolled up with Windows Workflow does all that now (i must admit i bet them to it)