QDoc Structure Reference > Events Files > Events File Example (1.1)
  
Events File Example (1.1)
The following is a partial sosomt-eB2_1.xml file in the QDoc 1.1 specification. Lines where three periods appear (...) show where lines have been removed for simplicity. A description of relevant document contents follows the file.
<?xml version="1.0" encoding="UTF-8" ?>
- <apicontroller xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ieli08.qad.com/apimodel/xmlenginexml/events/apicontroller.xsd">
<program name="String" mfgprobase="String" delta-version="String" description="String" default-operation="M" />
- <iterations>
- <field uid="soNbr#0:a021" name="so_nbr" inheritevents="true">
<IterationEvent iterationname="salesOrder" exititeration="f4" />
</field>
- <field uid="cdRef#0:cmmt01021" name="cd_ref" inheritevents="true">
<IterationEvent iterationname="salesOrderTransComment" exititeration="f4" />
</field>
...
- <field uid="iedLine#0:a051" name="ied_line" inheritevents="true">
<IterationEvent iterationname="orderLineDetail" exititeration="f4" />
</field>
</iterations>
- <operation action="R">
- <events>
- <field uid="soOrdDate#0:b0121" name="so_ord_date" inheritevents="false">
<DeleteEvent promptfield="delYn#0:1" sendvalue="true" actionkey="return" />
</field>
...
- <field uid="sodlcRef#0:line_det0101" name="sodlc_ref" inheritevents="false">
<DeleteEvent promptfield="delYn#0:1" sendvalue="true" actionkey="return" />
</field>
</events>
</operation>
- <operation action="A,M,S">
- <events>
- <field uid="line#0:c051" name="line" inheritevents="true">
<FirstEntryEvent prekey="f4" sendvalue="true" postkey
"return" />
</field>
- <field uid="work2Feature#0:w491" name="work2_feature" inheritevents="false">
<ChooseEvent />
</field>
- <field uid="work2Comp#0:w091" name="work2_comp" inheritevents="false">
<ChooseEvent />
</field>
</events>
</operation>
- <mappings>
<field-map uid="soTaxc#0:set_tax1881" nodename="soTaxc1" />
<field-map uid="soTaxable#0:set_tax1881" nodename="soTaxable1" />
<field-map uid="pMsgConfirm#0:2" nodename="pMsgConfirm1" />
<field-map uid="pMsgConfirm#0_INTRANS:1" nodename="pMsgConfirm2" />
<field-map uid="pMsgConfirm#0_INTRANS:2" nodename="pMsgConfirm3" />
<field-map uid="sodSite#0:c_btb_site1551" nodename="sodSite1" />
<field-map uid="sodTaxc#0:set_tax17131" nodename="sodTaxc1" />
<field-map uid="sodTaxable#0:set_tax17131" nodename="sodTaxable1" />
<field-map uid="pMsgConfirm#0_CONS2:2" nodename="pMsgConfirm1" />
<field-map uid="pMsgConfirm#0_INTRANS2:1" nodename="pMsgConfirm2" />
<field-map uid="pMsgConfirm#0_INTRANS2:2" nodename="pMsgConfirm3" />
</mappings>
</apicontroller>
The first set of entries in the events file are the iterations. The first iteration starts on the field so_nbr for the iteration salesOrder. The second iteration is the transaction comments iteration in the same order as in the data file. In QDoc syntax specification 1.1 each transaction comment section—if a child of a different parent—has a different node name. Therefore the parent node is used as a prefix to TransComment; for example salesOrderTransComment. Each iteration is identified by QAD Enterprise Applications field, iteration name, and the key required to exit the iteration.Following the iterations is the delete event and the first entry event fields. Delete fields require a field name, the value to send to confirm the deletion, and the key to complete the deletion.The mappings section contains the mappings between the unique identifiers that are assigned by QGen and the node names. While the nodenames are editable, the field-map IDs are not.