My Oracle Support Banner

Error message automatically sent to response queue when workflow fails with an error. (Doc ID 530211.1)

Last updated on FEBRUARY 06, 2019

Applies to:

Siebel System Software - Version 6.0.1 [2848] and later
Information in this document applies to any platform.

Symptoms

When Workflow Process or Business Service, is dispatched by the  "ReceiveDispatchSend" method of the EAI Transport (e.g the MQ Receiver) is terminated because of exception (execution error or stop step),
the text of the returned message is always combined of standard elements (slightly depends on Siebel release)
 
    1. Error prefix (e.g. "[0]" - the error number in the error stack)
 
    2. Error text of standard message or custom message (as it was used in the "Stop" step of the Workflow Process of the "RaiseErrorText"/"RaiseError" application method of Business Service)
 

    3. Error suffix with the error code - e.g. the "(SBL-BPR-00131) (WF_ERR_CUSTOM_1)" for the "stop" step with the WF_CUSTOM_1 error code selection.


Then set up a workflow process to call the business service. The In/Out field of the <Value> process property is set to In/Out but I did not reference it anywhere else in the workflow.

As result, in case of the Messaging System Transport Services (such as the "EAI MQ Series Server Transport" BS), the  NON-XML-conformed text message (UTF-16)  is returned.
 
So the external application consumer, has to expect to parse non-XML text messages form the response Queue to identify an error reporting from Siebel  Application side.

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!


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