A Job definition must not have a monolithic structure. Actions can be distributed onto multiple files, so-called Fragments that must each be integrated into the main Job definition by a corresponding xi:include.
<?xml version="1.0" encoding="UTF-8"?>
<jobdefinition name="testJob" model="\\localhost\JobServer\models\base.eox" xmlns:xi="http://www.w3.org/2001/XInclude">
<fileTrigger>
<failedFolder value="\\localhost\JobServer\failed" />
<incomingFolder value="\\localhost\JobServer\incoming" />
<outputFolder value="\\localhost\JobServer\success" />
<filter value="*.imx" />
</fileTrigger>
<actions>
<action name="Engineering.ImportIMXCommand" arguments="List{trigger.filePath}" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="includedJobDef.xml"/>
</actions>
</jobdefinition>
<actions>
<action name="T_Ecad_Ui.UpdateExtensions" arguments="List{absRef('Feeder.Mechatronik')}"/>
<action name="Engineering.ExportPXCommand" arguments="List{'Feeder','\\\\localhost\\JobServer\\results\\Feeder.px',true}" />
</actions>