Step 2 Individual Response Validation Route

This route validates the 271 response transactions received from the back-end system, stores the transactions in the data storage, and removes the corresponding 270 request transactions from the data storage.

Route Structure

Step 2 Individual Response Validation Route

Route Components Description

Component Name Component Type Description
Response from backend FS Inbound Receives 271 response transactions from the backend (Back End Emulation Route).
Get Ind Req Data Storage Inbound

Verifies if the data storage contains the 270 request assosiated the current 271 response. The component extracts the 270 request by using the XEServer property EdifecsInqID to identify the request.

This processing step in combination with the route components Request extracted?, Clear Body, and Aggregate Indv makes up a common route processing pattern that can be used to process only those data items (271 response transactions) whose dependent parts (in this case, 270 request transactions) are available in the data storage.
Clear Body Velocity

Сlears the message body for every XEServer message that carries a 270 request from the data storage.
Request extracted? Router Directs the 271 response further down the route only if the related 270 request was successfully extracted from the data storage.
Aggregate Indv Aggregation If the related 270 request was extracted successfully, the component batches an empty message and the message with the 271 response.
Response Validation Native Processing Validates the 271 response transactions and creates reports if an error occures.
Add Indv Resp Data Storage Outbound Stores the validated 271 response transactions in the data storage.
Remove request Data Storage Inbound After a valid 271 response is stored in the data storage, the component removes the associated 270 request from the data storage.
Report FS Outbound Stores error reports if any have been generated during the response validation.
Bad Response FS Outbound Stores 271 response transactions that have failed to pass the XEngine validation.