skip to main content
Corticon Server: Integration & Deployment Guide : Service contract examples : Examples of XSD and WSDLS available in the Deployment Console : 1 Vocabulary-level XML schema, FLAT XML messaging style : 1.2 CorticonRequestType and CorticonResponseType
 

Try Corticon Now
1.2 CorticonRequestType and CorticonResponseType
The CorticonRequest element contains the required input to the Decision Service:
<xsd:element name=CorticonRequest type=tns:CorticonRequestType />
The CorticonResponse element contains the output produced by the Decision Service:
<xsd:element name=CorticonResponse type=tns:CorticonResponseType />
 
<xsd:complexType name=CorticonRequestType>
  <xsd:sequence>
Each CorticonRequestType must contain one WorkDocuments element:
<xsd:element name=WorkDocuments type=tns:WorkDocumentsType />
</xsd:sequence>
This attribute contains the Decision Service Name. Because a Vocabulary-level service contract can be used for several different Decision Services (provided they all use the same Vocabulary), a Decision Service Name will not be automatically populated here during service contract generation. Your request document must contain a valid Decision Service Name in this attribute, however, so the Server knows which Decision Service to execute…
<xsd:attribute name=decisionServiceName use=required type=xsd:string />
This attribute contains the Decision Service target version number. While every Decision Service created in Corticon Studio will be assigned a version number (if not manually assigned), it is not necessary to include that version number in the invocation unless you want to invoke a specific version of the named Decision Service.
<xsd:attribute name=decisionServiceTargetVersion use=optional
type=xsd:decimal />
This attribute contains the invocation timestamp. Decision Services may be deployed with effective and expiration dates, which allow the Corticon Server to manage multiple versions of the same Decision Service Name and execute the effective version based on the invocation timestamp. It is not necessary to include the invocation unless you want to invoke a specific effective version of the named Decision Service by date (usually past or future).
<xsd:attribute name=decisionServiceEffectiveTimestamp use=optional
type=xsd:dateTime />
</xsd:complexType>
<xsd:complexType name=CorticonResponseType>
<xsd:sequence>
Each CorticonResponseType element produced by the Server will contain one WorkDocuments element:
<xsd:element name=WorkDocuments type=tns:WorkDocumentsType />
Each CorticonResponseType element produced by the Server will contain one Messages element, but if the Decision Service generates no messages, this element will be empty:
<xsd:element name=Messages type=tns:MessagesType />
</xsd:sequence>
Same as attribute in CorticonRequest. This means that every CorticonResponse will contain the Decision Service Name executed during the transaction.
< xsd:attribute name=decisionServiceName use=required
type=xsd:string />
Same as attribute in CorticonRequest.
<xsd:attribute name=decisionServiceTargetVersion use=optional
type=xsd:decimal />
Same as attribute in CorticonRequest.
<xsd:attribute name=decisionServiceEffectiveTimestamp use=optional
type=xsd:dateTime />