Raghukatta:
Hi,
> my application is desktop application.
Everything mentioned by Marsha is applicable to web applications.
For the desktop application you should examine the given dialog window in the Object Browser and try to find objects' identification parameters that are language independent and use them for NameMapping / object identification via FindChild().
For example, the system dialog window most probably will be of WndClass = '#32320' with the OK and Cancel buttons having IDs of btnOK and btnCancel accordingly (if I remember it correctly). In this cae your test code can reference them as
Sys.<process>.Window('#32320').Window('btnOK') that is language independent.
In the worst case when some given object cannot be stably and reliably identified without some language-dependent information, you may consider NameMapping configurations (https://support.smartbear.com/viewarticle/80669/).