Question
SeniorLink
US
Last activity: 16 Oct 2018 12:03 EDT
Dates prior to 1937 gets converted to a future date
In a DateTime UI control when a date is entered in format 03/02/1937 it gets converted to 03/02/2037 in the back end even as a text.
any idea why ? it does not happen when a date entered after year 1937.
Edit validate NotFutureDate fails for those dates..
Thanks for any help
Parbati Bose
<Removed personal information>
***Moderator Edit: Vidyaranjan | Updated Categories & edited personal information***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
Hello Parbati,
Can you verify your Editvalidate rule.
Below is the reference discussion to avoid future dates hope this helps you to resolve the issue.
https://pdn.pega.com/community/pega-product-support/question/not-showing-future-dates
Thanks
Sai
Vodafone
IN
Please ignore the last comment
Pegasystems Inc.
IN
Hi Parbati,
I tried it at my end and see that everything works fine.
Could you please confirm the Pega version used at your end and send screenshots of the issue as well as the Calendar used in the application for our review?
Thanks,
Gisela
SeniorLink
US
@Gisela_R
I am using Pega 7.2 I have uploaded the screenshot.
when I use the calendar this issue dont happen. when I enter the date manually for example 02/03/36 then only it happens.
edit validate rule is out of the box NotFutureDate
Here is the java code snippet for rule
Thanks for any help
Parbati
Pegasystems Inc.
US
Hi Parbati,
I had tested your use case in Pega 7.2 by creating a sample Date property and added NotFutureDate edit validate rule to it then used this property in the section with Post Value action during change event, but it is behaving as expected shown in the attachment with 03/02/1937 date.
You can share the tracer log of your use case for our further analysis as the issue is not reproducible in house.
Regards
Mahesh
Accenture
US
Hi Mahesh,
Did you give the year 1937 as is or did you just try to give 37??...
We are not having an issue when we give 1937 as the year. But when we give the input as 37 (ex:05/15/37) then it coverts to 2037 instead of 1937...
Please Let us know if you have any inputs on this.
Thanks
Charan
Pegasystems Inc.
US
Hi Charan,
I had tried with 05/15/37 which gives me "Enter a valid past date" error in the UI. Could you share the screen shot of your configurations for the Cell properties.
Regards
Mahesh
SiXworks Limited
GB
Sounds like an issue with the date formatting somewhere down the line...Interesting article which may help you can be found here:
It details the difference between YYYY and RRRR formats and may shed some light on your issue?