@AVINASHL4108 

This behavior is coming from browser and not from Pega.  You can see the same behavior outside Pega.

To overcome this behavior specifically in Pega application, you need to disable autocomplete feature with the DSS setting available in Pega.   

"prconfig/initialization/disableautocomplete/default" in RS:Pega-ProcessCommander, Owning Ruleset is Pega-Engine and the value is true

This setting prevents client-side storage of user name and password combinations. Use this setting in conjunction with clearing any existing stored sensitive information in the browser.

You can see other user question in this forum post.

Please refer the below article:

https://docs-previous.pega.com/security/85/understanding-dynamic-system-settings

In the article it refers to different control you can find a workaround.

You can write custom script to block the autofill values for which pega support cannot be provided.

https://stackoverflow.com/questions/10938891/disable-form-autofill-in-chrome-without-disabling-autocomplete

Note that this autocomplete tag is not supported for text input fields and for that we have raised an enhancement request FDBK-83421.