Sep 10, 2016

on Leave a Comment

OA Framework 12.2.5 Update 6 is out, but...only 2 fixes ?


From Oracle blog news released that OA Framework 12.2.5 Update 6 is available now.

What's new in this update?


  • The table header content overlapped with the records present at the immediate row when there is a specific personalization on the page.
  • In environments with Multi-Org Access Control (MOAC) enabled, the List of Values (LOV) search returns empty results with a newly added search query filter while creating a personalized view.
  • On specific JTT Interop pages, the LOV search window opens up only on double click if the LOV is dependent on the Partial Page Refresh (PPR) enabled field.
BUG 21465867 - DATE/TIME PICKER DOES NOT VALIDATE TIME ENTRY 


Quoted from this Steven Chan's blog, the new stuff includes



This bundle patch is cumulative: it includes all fixes released in previous EBS 12.2.5 bundle patches.

This latest bundle patch includes new fixes for the following critical issues:

But according to the README of this patch:

==================================================
Bugs Fixed
==================================================
The following bugs are fixed by this patch:
22590683 - FORWARD-PORT 21465867 TO 12.2.5
24398948 - CUSTOMER NAME MISALIGNED

Just two fixes and you give me a full bundle release ?  Are you serious ?

I'd checked up What is bug 21465867, as mentioned that this fix is ported to 12.2.5, becomes bug fix 22590683.

Description
Spinbox validation on the DateTime Calendar window are not been invoked, and
this allows user to potentially enter any number which is out of the range in
the Hours, Minutes and Seconds spinbox input.
By design, SpinboxBean always have a DecimalValidater attached to it, and the
validation occurs upon form submit. However, as the DateTime Calendar window
does not trigger any form submit, so the validation logic is bypassed.

Who log this bug ? Not surprise, customer name started with G  -- the top ten customer, very top.

So you justify whether you should apply this patch to your 12.2.5 instance.  I will say…not this time.

0 comments: