My Oracle Support Banner

How To Change The Casing Of ERROR Tag In The Response Message Of An Inbound REST Call (Doc ID 2771675.1)

Last updated on MAY 13, 2022

Applies to:

Siebel CRM - Version 19.1 and later
Information in this document applies to any platform.


Calling a business service via Inbound REST Request, results in a Response with an ERROR Tag.
This tag does not meet the PascalCasing naming convention.


The issue can be reproduced at will with the following steps:
1. Business service invokes a framework workflow to process an Inbound REST Request.
2. This workflow processes the Inbound Request.
  a. In case of success, this workflow is ended as expected via an 'End' step. The response returns an HTTP 200 status code and contains the response message (the naming convention of the message tags from the workflow is controlled).
  b. In case of a failure this workflow ends up in an error exception which points to a 'Stop' step. This stop step throws an error message and error code. The response returns an HTTP 500 status code and contains the error message and error code in the 'ERROR' tag.
  Because it is returned in ALL CAPS, it does not meet the PascalCasing naming convention for request and response message structure.


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

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