Purpose : This how-to guide will provide step-by-step instruction on setting up Custom Header in IFS REST— Partner Connector in Boomi to Support IEEE Standard 754. Setting up the custom header and its value as mentioned in the following sections of this article will help you to address integration issue due to diverse floating-point implementations withing the system.
Instructions to set Custom Header while using IFS REST— Partner Connector Defining the "Content-Type" and "Accept" headers with "IEEE754Compatible=true" in Set Properties step before the Connector could leverage the benefits of the IEEE 754 standard.
Follow the instructions given below to implement this:
- Add a "Set Properties" step before the IFS REST Partner Connector
- Define the following headers in the "Set Properties" step. The "inheader_" prefix will add these headers to the request.
| Property Type | Property Name | Property Value |
| Dynamic Document Property | inheader_Content-Type | application/json;IEEE754Compatible=true |
| Dynamic Document Property | inheader_Accept | application/json;IEEE754Compatible=true |
- Define the binary and decimal floating-point data in the payload as strings if they exist.
*** The Number type fields in the request or response profiles defined under the operation will still have the data type set as Number. To use these fields in subsequent steps, you need to change their data types to "Character". Although the data type of the number field is Number, you will receive the response as Character if you set the "Accept" header to "application/json;IEEE754Compatible=true". Therefore, instead of manually changing the data type of the Number fields, you can download the response payload and reimport the response profile.