Execute an Adapter service with InputFieldType (in the Which tab) 'java.lang.Byte' by providing a value that exceeds the limit, an error message appears informing the same. Later, if you execute the same Adapter service by changing the InputFieldType to 'java.lang.String', the same error message appears preventing the service execution, even if you provide correct values.

This issue is now fixed.

In a transformer, if the output variables (Pipeline Out to Service Out or the reverse way)are mapped before the input variables (Pipeline In to Service In or the reverse way), the map step containing the transformer saves an incorrect value and hence, the flow service fails with incorrect results.

This issue is now fixed.

When using Designer to invoke the pub.flow:setResponseCode service, if the responseCode input variable value is set to 204, the Results view displays an exception.

This issue is now fixed.