Identifying and verifying the source of the cXML data is only the first step in ensuring proper data flow between the website and the MIS system. Linking the details of the request itself and the end-user customer who made that request are also vitally important.

The <Request> portion of the cXML file provides these links through the use of additional IDs. The first is the <OrderRequest> or <RFQ> ID.

    
Order
    <Request>
     
            <OrderRequest>
                <OrderRequestHeader orderDate="8/27/2009 1:25:18 PM" type="new">
                <ID domain="ws4p">446511</ID>
                
    
RFQ
    <Request>

            <RFQ>
                <RFQHeader requestID="907528" requestDate="08/25/2009 15:28:32" type="new">
                <ID domain="ws4p">907528</ID>

In both examples above, the source (domain) of the <ID> is identified, so the receiving system (in this case, the MIS) knows the context of the ID coming in.

If the request type is "new," it then generates a new ticket and inserts this ID in the appropriate field within the database table to match up its own ID (e.g. Project_ID) with that of the other system (in this case, the website) (e.g. Website_Project_ID).

Future transactions involving this same ticket will then include both IDs (the one generated by the website and the one generated by the MIS system), so both systems can access this information seamlessly.

                <ID domain="ws4p">907528</ID>
                <ID domain="Test MIS">89642873</ID>

Note: If no field currently exists within your system's table structure to accept the incoming ID from the website, one must be added, in order to make this integration work.