E1: ORCH: Form Extension and Logic Extension thru Associate Orchestration Not Allowing Output to Form Control Field after Disable Control Function is Called
(Doc ID 3011242.1)
Last updated on MARCH 19, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Form Extension and Logic Extension (LEX) is not allowing output to Form Control fields after calling "Disable Control" Form Control Function.
User is trying to call a LEX inside a Form Extension on Customer Master Revision form (P03013|W03013B) in "Post Dialog is Initialized" event.
For this example, within the LEX, there is an Assignment Block step to assign a form control field (Payment Instrument RYIN) with a value of '?'. Then, a Form Control Function "Disable Control" is called after the Assignment Block.
If "Disable Control" function is called, the output value is wiped out and the output value '?' is not displayed.
If the "Disable Control" function is not called in LEX, then the output value '?' is send back to the form control field correctly.
If similar event rules are done within Form Design Aid (FDA) on "Post Dialog is Initialized" event, then the output value '?' can be assigned even after Disable Control() system function is called.
LEX should behave same way as the FDA event rules.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |