#27241 OpenAPI: Error although query successful

enhancement

critical

#25645

OpenAPI server

#26207

REST calls via TL script to external APIs according to OpenAPI specification

major

#27196

DeepL: Use glossaries for translations

#27214

TL-Script unversioned object comparison

#27215

Historical to-n references

#27234

Include ChartJS and OpenAPI in BPE Standard Configuration

minor

#26835

Perform instanceof checks unversioned

#26935

Make Close dialog configurable by Create

#27225

Bulk Dependency Update

#27236

Model definition for revision

#27251

TLModelUtil: Replace declared ConfigurationException with TopLogicException

defect

critical

#27205

TL-Sync transmitter stops on association update

major

#27139

Button menu in button bar does not open

#27207

Search suggestions of SelectFields and popups of the breadcrumb are placed incorrectly

#27228

Missing display of Flex data for historical objects

#27241

OpenAPI: Error although query successful

minor

#26797

Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)

#26921

ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.

#27096

Tree does not scroll the selected node into the viewport on (external) selection

#27167

Normalizing JSPs leads to wrong indentation for if-else blocks

#27203

Application tests with chart.js report on home page fail

#27204

PersistentEnumeration.tValue(...) leads to ClassCastException

#27218

Grid tables: Calculated column: Single-Value SelectField requires list value.

#27227

User time zone and thus SubSession time zone can be zero

#27231

Incremental modification of a set-valued attribute not possible.

#27239

Typo in database configurations at "password template

#27240

OpenAPI: Missing content type for JSON request content

#27249

TLScript suggestions are always displayed in the same language

#27250

Missing Maven profile "ide" in Eclipse

defect

major

#27241

OpenAPI: Error although query successful

IntegrationAPI

In principle, 2xx HTTP status codes indicate "success." However, a request that returns, for example, a 204 "No content" status code will cause the application to crash.

There is no way to explicitly respond to HTTP status codes. You can only either expect a JSON object or configure a built-in request check.

Improvement

Special post-processing can be configured for a range of status codes, specifically the 1XX, 2XX, 3XX, 4XX, and 5XX status code ranges. If the response does not have one of these status codes, the default handler is used:

Test

Configure an OpenAPI server as a target that returns responses with different status codes.
Configure different handlers for these.
- Expected Behavior: The handler configured for the response’s status code is executed.