In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Updating Events Files
    The events files in QXI are .xml files containing program-specific keystroke and navigation. Events files for each QDoc-supported program are shipped with the product or are generated by the QGen product. You can maintain multiple copies of the events files for each QAD Enterprise Applications program to support either different paths through a program, or to test incremental performance improvements in update paths.
    These files must first be copied to the custom events directory; then a new event and the new program name must be added.
    1
    Copy the events file you want to modify to the custom directory. The following example is for sales orders. Copy from:
    TOMCAT_HOME /webapps/<QXI webapp>/WEB-INF/events/eB2/sosomt-eB2_1.xml
    to:
    TOMCAT_HOME /webapps/<QXI webapp>/WEB-INF/events/eB2/custom/sosomte-B2_1.xml
    2
    Edit the events schema file to add a new IterationEvent. The event must have an attribute of either preprocess or postprocess. This attribute defines the custom program to call when the iteration event is encountered. Use the following code fragment showing a preprocessing program as a model:
    <field uid="soNbr#0:a02" name="so_nbr" inheritevents="true">
    <IterationEvent iterationname="salesOrder" exititeration="f4" preprocess="xxMyPreProg.p"/>
    </field>
    This sample runs xxMyPreProg.p before processing the QDoc.
    An equivalent postprocessing program call would appear as follows:
    <field uid="soNbr#0:a02" name="so_nbr" inheritevents="true">
    <IterationEvent iterationname="salesOrder" exititeration="f4" postprocess="xxMyPostProg.p"/>
    </field>