My Oracle Support Banner

OpenAPI Swagger Doc Created For Inbound REST Creates Element Names With "External Name" While Runtime Output Uses IC Field Name (Doc ID 2657426.1)

Last updated on MAY 01, 2023

Applies to:

Siebel Call Center - Version 20.1 and later
Information in this document applies to any platform.


OpenAPI swagger doc created for Inbound REST creates element names with spaces in it

Take an existing Integration Object that is exposed as REST. For Example Base Service Request. Under Integration Component "Service Request" as an example take the field Account Status. The XMLtag for this field is AccountStatus. In old SIebel, the generated WSDL to make an inbound Soap Request uses the XMLtag to create the elements. But with IP2017, when generating the openAPI/swagger doc using describe, the XSD file created has the Field Name Account Status used instead of XMLtag as the element name.

The issue can be reproduced at will with the following steps:
1. Go to Postman
2. Send below REST request to describing an IO
https://hostname:port/siebel/v1.0/data/Service Request/Service Request/describe

3. Siebel generates  openAPI/swagger doc with the element names with spaces in them. This is incorrect from an XML naming convention and this cause the application trying to consume to fail on this.




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.