@Vishal Venkatesh

I understand that you are experiencing an issue with the DateTime control property and its default time value. I apologize for this inconvenience and will do my best to provide you with an effective solution. 

After reviewing the issue, I have identified a possible root cause for the problem. It appears that the issue is related to the way the system handles time zone conversions for certain year ranges. Specifically, when the year is less than 2039 and the time zone has a positive offset from GMT, the system is adjusting the time value by one hour to account for daylight savings time, which was not in effect in India prior to 2039. 

To address this issue, I recommend using a time zone with a fixed offset from GMT (such as GMT +5:30) instead of a time zone with a variable offset. Additionally, you may want to consider using the FormatDateTime function with a custom date format to ensure that the time value is consistently displayed in the desired format.

Another solution to this issue could be to create a custom Java function that will handle the time zone conversion for you. This function can be called from the DateTime control property, ensuring that the correct time value is displayed for all year ranges. This approach may require some additional development effort, but it should provide a more robust and reliable solution in the long term.

If none of the above solutions work, I recommend contacting Pega support for further assistance. They will be able to provide you with more in-depth technical guidance and assistance in resolving the issue.