Timestamp attribute allows malformed years like Apr 2, 202, 12:00:00 PM

Aravind Allam

(7●2●4●4) edited

Apr 02, 6:50 a.m.

I have a workitem attribute of type timestamp called Date

The field accepts dates like:

Apr 2, 202, 12:00:00 PM

Apr 2, 2026, 12:00:00 PM

Ideally, the system should only accept valid years in the 4-digit range(1000-9999).

The value Apr 2, 202, 12:00:00 PM is malformed and should not be allowed, but it currently passes validation.

Is there a built-in way to prevent malformed dates like Apr 2, 202, 12:00:00 PM

for Timestamp fields in RTC 7.0.3

If not is there any recommended approach to enforce this constraint reliably?

0 votes

0 answers

79 views

0 votes

Be the first one to answer this question!

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers

Answers and Comments

Question details

rational-team-concert

× 43,062

clm

× 7,608

configuration

× 6,175

workflow-management

× 1,761

elm

× 1,437

Question asked: Apr 02, 6:37 a.m.

Question was seen: 79 times

Last updated: Apr 02, 6:50 a.m.

Timestamp attribute allows malformed years like Apr 2, 202, 12:00:00 PM

Aravind Allam

0 answers

79 views

0 votes

Be the first one to answer this question!

Follow this question

Question details

Related questions