Corticon response is incorrect since the request is missing some integer fields when executing against a decision service deployed to .NET Server

The solution is built based on the .NET WCF Client example

Fields like orderId, quantity etc are missing in the request
These fields are all defined as non mandatory,nullable fields in the WSDL [ i.e. nillable="true" minOccurs="0" ]
E.g. 
<xsd:element name="orderID" type="xsd:long" nillable="true" minOccurs="0" />
<xsd:element name="quantity" type="xsd:decimal" nillable="true" minOccurs="0" />

Since the request to Corticon is incorrect, the wrong rules fire and the response is incorrect

When minoccurs=0 for a field, svcutil.exe will generate "Specified" field. 

To resolve the issue of missing integer/decimal fields in the request that resulted in the incorrect response :

a] Comment out all the methods in Stub ( generated from the WSDL using svcutil.exe) related to integer/decimal fields related to the Entity in the Corticon request
For e.g.
// private bool orderIDFieldSpecified;
// private bool quantityFieldSpecified; etc

Or

Remove the "minOccurs=0" for the fields [ e.g. orderID and quantity] in the WSDL and then generate the stub using svcutil.exe. Then the generated stub will not contain the "Specified" property for every attribute.

Or

Ensure orderIDSpecified = true; quantitySpecified = true in the application code whenever orderId , quantity fields have an assigned value in the application code

b] After making these changes to the stub/application, execute against the decision service and we  now see the expected input request being sent to Corticon and the expected response.

See  When using “svcutil” with “/wrapped” parameter to generate client stubs from Corticon WSDL with full set of Corticon types, the entity attributes are not serialized when sending request