Step 2 Individual Response Validation Route

This route validates the 277 responses received from the back-end system, stores the responses in the data storage, and removes the corresponding 276 requests 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 277 responses from the backend (Back End Emulation Route).
Get Ind Req Data Storage Inbound

The component verifies if the data storage contains the 276 request that produced the current 277 response. The component extracts the 276 request by using the XEServer property EdifecsInqID to identify the required request.

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

For every XEServer message that carries a 276 request from the data storage, the component clears the message body.

Request extracted? Router Directs the 277 response further down the route only if the related 276 request was successfully extracted from the data storage in the previous step.
Aggregate Indv Aggregation If the related 276 request was extracted successfully, the component batches an empty message and the message with the 277 response.
Response Validation Native Processing Validates the 277 responses and creates reports if there are errors.
Add Indv Resp Data Storage Outbound Stores the validated 277 responses in the data storage.
Remove request Data Storage Inbound After a valid 277 response is stored in the data storage, the component removes the associated 276 request from the data storage.
Report FS Outbound Stores reports if there are errors.
Bad Response FS Outbound Stores 277 responses that failed to pass the XEngine validation.