Details
-
Type:
Bug Fix
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.4
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Rice Module:KRAD
-
Sprint:2.4.0-rc1 Sprint 8
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Code Review Status:Not Required
-
Include in Release Notes?:Yes
Description
The date of lookup with an exact date criteria field doesn't match existing records.
- KRAD Demo -> Travel Account Lookup
- Enter an existing "Date Created" (eg 04/01/2014) and search
- Notice that no records are returned even though they do exist.
Attachments
Issue Links
- discovered by
-
KULRICE-13678 2.4.0 Coordinated Developer Testing (4/2/2014)
-
- Closed
-
Activity
Simplest solution is changing the LookupCriteriaGeneratorImpl to handle single date checks as between date at midnight and date at 11:59pm:
addBetween(criteria, propertyName, parseDate(LookupUtils.scrubQueryCharacters(propertyValue)), parseDateUpperBound(LookupUtils.scrubQueryCharacters(propertyValue)));
but I have some reservations if this will then affect the use of date with time searches criteria or performance on search results by using a date range over a single value.
Tested on env14 and reproduced issue. Checked on local environment manually and using DemoTravelAccountLookUpAft:testTravelAccountLookUp. CREATE_DT is a datetime field in the TRV_ACCT table. Appears the field is being evaluated as datetime comparison and not relaxed date comparison. Found the predicate between evaluated was:
The date was formatted as such by the CriteriaSupportUtils.determineCriteriaValue
To confirm it is an exact datetime check, replaced LookupCriteriaGeneratorImpl.addDateRangeCriteria handles of equals to check between beginning of the day and end of the day and worked correctly.