SOAP Fault Does Not Populate Faultstring / Faultcode Of The Proxy Business Service in Task Based UI (TBUI)
(Doc ID 2487772.1)
Last updated on FEBRUARY 06, 2019
Applies to:Siebel Financial Services CRM - Version 16.16 [IP2016] and later
Information in this document applies to any platform.
On : 16.16 [IP2016] version, Client Functionality
SOAP Fault does not populate faultstring / faultcode of the Proxy Business Service
When Outbound Services is invoked from Task Based UI .
The service works fine but the Proxy BS does not interpret the 'Soap Fault' sent back the external application.
Outputs properties faultcode / faultstring / XMLHierarchyOutput are not properly populated.
Instead the Proxy BS raise an SBL-EAI-04308 error and populate the TBUI properties ‘Error Code’ and ‘Error Message’.
The issue can be reproduced at will with the following steps:
1. create a task based ui and call an outbound web service as a step in the task.
2. Use inputs that cause a SOAP Fault.
3. Notice the siebel error code is populated, but the faultstring and fault code task properties are not.
The issue has the following business impact:
Due to this issue, users cannot implement error handling for this TBUI and complete acceptance tests of this new custom functionality.
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