My Oracle Support Banner

OPA: Error Stack Referencing Errors Thrown by Last Input Parameter but not Referencing Errors from First Input Parameter (Doc ID 2462289.1)

Last updated on OCTOBER 18, 2018

Applies to:

Oracle Policy Automation - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.9 version, Oracle Policy Automation

Error stack is referencing errors which are thrown by the last input parameter but not referencing errors from the first input parameter


OPA Version: Oracle Policy Automation 18B (Build 65)

OPA Cloud Versiobn: Oracle Policy Automation 18B (Build 73)

Problem Statement: In OPA transaction, if there is a failure in OPA pricing call due to multiple incorrect input attributes, the error stack was holding only errors which was thrown at the last attributes (last attribute which caused error). The error stack should hold information about all the attributes which caused the error.


ERROR
-----------------------

No errors but references to the error are not accurate


STEPS
-----------------------
Let us assume we have two input attributes A and B. The valid values of A should be between 1 to 5 and the valid value for B is B should be decimal number. Let the output parameter be C.
Now when we pass some invalid value for A say 6 and valid value for B say 12.0, it will make an OPA call, though some web services. The payload o the web service will have error stack trace saying the "Invalid value '6.0' for attribute 'A' in instance 'global[TRANSACTION_002]'. Reason: Value Should be Between 1 to 5".

Now let us consider a scenario where we will pass valid value for A but some invalid value for B say "ABC". In the case the payload will have the error stack as "Error reading attribute 'B': Bad Request: Cannot parse attribute value: Value 'ABC' is not a valid decimal".

Now let us consider a scenario where I will pass invalid values for both A and B, say the value for A is 10, and for B is DEF". In this case the payload will have error stack trace, which say " Error reading attribute 'B': Bad Request: Cannot parse attribute value: Value 'DEF' is not a valid decimal". In actual it should have display the error message with details. that the value of A was also incorrect along with the reason why A was incorrect. Basically which all attributes has caused the OPA transaction to failed should be available in the error stack trace.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.