Hi,
In Oracle Process Automation (OPA), for the approver page, the built-in Save button allows saving task data even when validation errors are present. When certain numeric values exceed a threshold (for example, Length/Width/Height > 1000), the task saves successfully but later reopens in a corrupted UI state where line-level fields disappear or appear blank.
This occurs even though the database columns and OPA attributes are defined as NUMBER with no precision limits.
Expected Behavior
- Either:
- Line-level fields should not disappear after reopening a saved task
Business Impact
-
Users unknowingly save invalid data.
-
Reopened tasks show broken UI.
-
Approvals cannot proceed.
-
Transactions may need to be abandoned or recreated.

-
On Entering a value the calculation written in onchange event of length width height and requested qty
calculates the total requested qty
If the total requested qty exceeds outstanding qty for the entered value it throws error
-

On click of save button

It says task details has been saved
But reopening the same record again , all the fields gets disappeared.
