Uses the Component: ResponseActionCriteriaType
ResponseCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned.
ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD's noun exemplar.
ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns.
That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated.
The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies.
Table 5.9. Fields and Components
| Name | Description | Occurrence | Type | Data Type | User Notes |
|---|---|---|---|---|---|
| ResponseExpression |
ResponseExpression identifies a pointer to the Component being provided as a response to a request. This point is provided using an appropriate value of the given expressionLanguage indicated. The actionCode is intended to indicate what has occured with the given component and/or instance of the given component. | 0..1 | Component | ResponseExpressionType | |
| ChangeStatus | 0..1 | Component | ChangeStatusType |
The XML Sample provided here is an approximation of the genrated XML for this component. Not all of the fields are required for implementation.
Example 5.9. ResponseCriteria
<ResponseCriteria>
<ResponseExpression>......</ResponseExpression> [0..1]
<ChangeStatus>......</ChangeStatus> [0..1]
</ResponseCriteria>