Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 Table of contents

Table of Contents

Null values

JSON messages with null values are supported by web service calls and Blueriq as a Service.

 JSON MessageDomain schema
BaaS requestProperty value nullProperty not required
BaaS responseProperty absentProperty not required
Web service request  
Web service response  

 

Incoming JSON messages containing properties with null values are allowed for non-required properties. When a property is specified as non-required 

When a response to a REST JSON web service call contains properties with null values these properties will be handled as non-existent properties. This means that null values are only accepted for properties that are specified as non-required in the response domain schema. Non-required properties on request domain schemas are not present in the actual request that the web service call creates, so there won't be any null values in web service call requests.

Responses

Blueriq as a Service

HTTP status codes

When working with Blueriq as a Service (BaasBaaS) there are several status HTTP status codes that can be expected in the response.

Response codeDescription
200OK
400The request could not be deserialized.
401A non-accessible flow is requested.
404An unknown web service is requested.
406The request contains an Accept accept header for an unsupported MIME type.
500An unexpected exception occured occurred while handling the request.

Non-required properties

JSON messages with null values are supported by web service calls and Blueriq as a Service.

The following table shows all situations regarding a non-required property (as modelled in the domain schema in Studio) which is not set (value UNKNOWN):

 JSON message
BaaS requestProperty absent or property value null
BaaS responseProperty absent
Web service requestProperty absent
Web service responseProperty absent or property value null