This section of the ERES administration allows the creation of rules to save registry users the task of reviewing the automatic entries of entries from the AOC services that are collected in the “Pending entries MUX (AOC)” tray.
These rules can be defined for both inputs and outputs, which arrive at ERES automatically through MUX and allow predetermining both the area or work unit to which the records will be sent for processing, and the procedure series to which they must be associated.
So, for example, if you want to define that all invoice entries go to a specific work unit existing in ERES and that, in addition, they are associated with a series in the Classification Table, you can create a relationship, similar to the one below, from the presentation route e-FACT, which is the AOC service through which the invoices arrive.
The same can be done for the outputs of the e-NOTUM service, to allow them to go to a specific work unit and not have to remain in the MUX pending records tray.
In the case of procedures that arrive through services such as EACAT or e-TRAM, you will be able to define, in addition to the submission method and procedure, the procedure related to the entry records.
Important : the values in the drop-down menus of this functionality, which allow you to define the data that will be automatically added to the records (the submission route, the procedure (MUX) and the procedure), are live fields that will be fed by the values of the inputs and outputs that arrive at ERES from the start of the functionality. That is, to define those relationships for which values must be identified beyond the submission route (the MUX procedure or the procedure), you will have to wait until you have received an entry in ERES of the type you want to configure, in order to create the predefined data relationship, which will apply to the successive ones.