A sample CorticonRequest payload is shown below. It is a Decision-Service-level message which means that only those Vocabulary terms used in the Decision Service are contained in the CorticonRequest. It is also HIER XML messaging style.

Notice the Decision Service Name in the CorticonRequest:

<CorticonRequest xmlns=“ urn:decision:tutorial_example ” 
      xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”
      decisionServiceName="tutorial_example">

Optional execution properties can be set in the request to override default values on the server. The available execution properties, set here to other than their default value, are as follows:

  <ExecutionProperties>
    <ExecutionProperty 
       name="PROPERTY_EXECUTION_RESTRICT_RULEMESSAGES_INFO" 
       value="true" />
    <ExecutionProperty 
       name="PROPERTY_EXECUTION_RESTRICT_RULEMESSAGES_WARNING" 
       value="true" />
    <ExecutionProperty 
       name="PROPERTY_EXECUTION_RESTRICT_RULEMESSAGES_VIOLATION" 
       value="true" />
    <ExecutionProperty 
       name="PROPERTY_EXECUTION_RESTRICT_RESPONSE_TO_RULEMESSAGES_ONLY" 
       value="true" />
    <ExecutionProperty 
       name="PROPERTY_EXECUTION_LOCALE" 
       value="fr-FR" />
    <ExecutionProperty 
       name="PROPERTY_EXECUTION_TIMEZONE" 
       value="America/Chicago" />
  </ExecutionProperties>

Notice the unique id for every entity. If not provided by the client, Corticon Server will add them automatically to ensure uniqueness:

<WorkDocuments>
     <Cargo id=“Cargo_id_1”>

Attribute data is inserted as follows:

         <volume>40</volume>
         <weight>16000</weight>
 
    </Cargo>   
  </WorkDocuments> 
</CorticonRequest>