[VELTOOLS-209] velocity 1.7 vs velocity 2.3: evaluation of scripts with empty value is not backward compatible

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0, 3.1
• Component/s: GenericTools
• Assignee: Unassigned
• Reporter: ambika
• Created: 25/Apr/22 22:52
• Updated: 24/Aug/24 10:50

Description

Script:     

 

  "vLATE_GATE_IN_6":"#set( $inTimeZone = $date.getTimeZone().getTimeZone('Europe/Berlin') )\n\n#set( $outTimeZone = $date.getTimeZone().getTimeZone('Asia/Shanghai') )\n\n#set( $locale = $date.getLocale() )\n\n#set( $myDate = $convert.parseDate(${*}

{lead.lateGateIn}

{*},\"yyyy-MM-dd HH:mm\",$locale,$inTimeZone) )\n\n${date.format('yyyy-MM-dd hh:mm a',$myDate,$locale,$outTimeZone)} "

note: lead.lateGateIn = "" in the values 

there are multiple other scripts vLATE_GATE_IN_5, vLATE_GATE_IN_4 but in the script vLATE_GATE_IN_4 , the values for convert.parseDate is given as below:

$convert.parseDate("2022-04-22") 

 

Issue: 

Older version of velocity evaluates the script vLATE_GATE_IN_6 to: 

Time):\\n\\n\\n\\n n2022-04-22 11:00 AM

 

Newer version of velocity evaluates the script vLATE_GATE_IN_6 to: 

Time):\\n\\n\\n\\n n${date.format('yyyy-MM-dd hh:mm a',$myDate,$locale,$outTimeZone)}