Suspense Screen Event/action Problems
(Doc ID 2508701.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Insurance Policy Administration J2EE - Version 126.96.36.199 and later
Information in this document applies to any platform.
On : 188.8.131.52 version, General
Suspense screen event/action problems
OnChange logic defined for the SuspenseScreen does not appear to function on the Split/Child Suspense pop-up.
On Split Screen when any field is updated, base logic populated MasterSuspenseGUID, which refreshes OnLoad logic(which if MasterGUID exists, shows payor and Stat.Co.)
-> once base logic is refreshed, OnLoad logic is reset to default Show/Hide,
-> such that Hidden field AccountNumber is shown at initial Onload, then base code sees a field has changed and refreshes, AccountNumber returns to hidden.
OnChange ASSIGN does not work with fields DataType = (combo or client). (Base SuspenseScreen page)
Screen appears to default back to hidden for fields listed as Hidden=Yes, unless explicitely told to 'SHOW'
1) On the split screen, if any field is updated and has OnChange logic associated, the expected actions do not occur. 2)OnChange on the standard screen will not ASSIGN a value to fields with DataType Combo or Client. Text fields are able to be assigned as expected. 3) When OnChange logic is invoked on standard screen, if a field is defined as Hidden=Yes, system will default field back to hidden unless explicitly stated not to.
The issue can be reproduced at will with the following steps:
1) Configure onchange logic for a field on the split screen. change field value. confirm Onchange does not fire.
2) Attempt to Assign a Combo or Client type field through Onchange Logic. Perform expected behavior. Notice assignment did not occur.
3) Define a field as hidden. Use onchange logic to display field. Perform another action that uses onchange logic. Notice first displayed field has defaulted back to hidden.
The issue has the following business impact:
Due to this issue, creates difficulty for user to validate information and to view appropriate fields for a variety of circumstances. Forces use of only OnLoad and on Submit events.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document