@VarunKumar303

OOTB pega localises all values on a section. Trying to prevent pega from doing this for your application is a lot of work and isn't worth the effort. For small sections it's doable, but takes some work. So this solution is more focussed on disabling localisation for a few properties, rather than for trying to change pega's behaviour for all user interfaces.

You can turn off localisation section by section by unchecking the localize option. Then you could include another section that does localise and add the property there.

The first section won't get localised, the included section will get localised. I wouldn't recommend doing this, as you'll have to disable localisation on every section you won't like to localise items.

A better approach in my opinion is to use the read only display on a property. When a property is included on a section, you can influence its behaviour using the read only options.

The default is set on Localise Property Value, but you can change this to Property Value and pega won't localise. I think this is a preferable solution, as the options are also available from AppStudio.

A third option you could think for not localising a property, is by saving the property with the 'Cannot be localised in UI controls' option.

We use this option for name properties. 

As long as you don't need to 'delocalise' a lot of properties, use the second approach. If for some reason you have a section with loads of properties on them, turn off localisation for the whole section.

And if you have properties you never want to localise, resave the property and turn off the localisation option.