Supported output parameter mappings
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
The following table indicates the supported output parameter mappings between HTTP response elements and ABL data types. Y and N indicate whether a mapping is supported or not. Assume any mapping not mentioned in these tables is not supported.
| ABL Data Types | HTTP Response | ||
|---|---|---|---|
| Status Code | Response Header (including cookie and location) | Response Body | |
CHARACTER
|
N | Y | Y |
LONGCHAR
|
N | Y | Y |
INTEGER
|
Y | Y | Y |
DECIMAL
|
Y | Y | Y |
DATE
|
N | Y | Y |
DATETIME
|
N | Y | Y |
DATETIME-TZ
|
N | Y | Y |
INT64
|
N | Y | Y |
LOGICAL
|
N | Y | Y |
MEMPTR
|
N | Y | Y |
RAW
|
N | N | N |
RECID
|
N | N | N |
ROWID
|
N | Y | Y |
WIDGET-HANDLE
|
N | N | N |
TABLE
|
N | N | Y |
DATASET
|
N | N | Y |
Note: ABL arrays (ABL variables defined with the
EXTENT option)
are encoded as JSON objects. see JSON input and output message formats for more information.