Bug #563

CORUS - EPF Resend date format

Added by Hafizudin MD almost 14 years ago. Updated about 13 years ago.

Status:Work Completed-End life cycleStart date:October 18, 2010
Priority:NormalDue date:October 20, 2010
Assignee:Nor Shuhaida Subri% Done:

70%

Category:-Spent time:2.00 hours
Target version:-

Description

no validation for this 01/01/201x , 1/1/1x

History

#1 Updated by Hafizudin MD almost 14 years ago

no validation for this 01/01/201x
 not follow dd/mm/yyyy (1/1/1)

#2 Updated by Nor Shuhaida Subri almost 14 years ago

  • Due date set to October 20, 2010
  • Status changed from New - Begin Life Cycle to Work Completed-End life cycle
  • % Done changed from 0 to 100

replace 'datePattern' to 'datePatternStrict' inside validation.xml

#3 Updated by Hafizudin MD almost 14 years ago

  • Status changed from Work Completed-End life cycle to Development / Work In Progress
  • % Done changed from 100 to 50

--not follow dd/mm/yyyy (1/1/1) - done-
-no validation for this 01/01/201x , 1/1/1x

#4 Updated by Hafizudin MD almost 14 years ago

  • Status changed from Development / Work In Progress to Work Completed-End life cycle
  • % Done changed from 50 to 100

-no validation for this 01/01/201x , 1/1/1x - done

tested by hafiz

all bug tested - ok

#5 Updated by Sarinah Darsy about 13 years ago

  • % Done changed from 100 to 70

There are problem when resend date file.

Kamaruddin said, when doing resend file we just need to replace the filename only. which is the HHMMSS should be replace by 999999, then 888888, then 777777 and so on.

But current corus flow that we have, when doing resend date file we actually create new file into server.

Also available in: Atom PDF