Translations - OPALE - Utilisation - Ordre de priorités des règles sur le moteur de règles MAPPING IBM-i/4/en
Différence entre versions
De MappingDoc
| Ligne 2 : | Ligne 2 : | ||
#: '''<u>MATCH</u>''' --> We look for the other parameters (user, job, reference, formtype, etc) the values different from *ALL and compare their values. '''Those which will have the more matching criterias with values different from *ALL will be executed.''' (Priority to the most selective rule). In the event where multiple rules have those same criterias, the first in the list will be taken and executed. | #: '''<u>MATCH</u>''' --> We look for the other parameters (user, job, reference, formtype, etc) the values different from *ALL and compare their values. '''Those which will have the more matching criterias with values different from *ALL will be executed.''' (Priority to the most selective rule). In the event where multiple rules have those same criterias, the first in the list will be taken and executed. | ||
#: '''<u>NO MATCH</u>''' --> Go to point 2 | #: '''<u>NO MATCH</u>''' --> Go to point 2 | ||
| + | |||
| + | #<span style="color:red">The engine search in the rules associated another '''match with the other parameters''' (Please note that the partiel name has the same effect as the other parameters. Example : INV* for INVOICE. Indeed there is no priority on the partiel spooled file name) .</span> | ||
| + | #: '''<u>MATCH</u>''' --> We look for the other parameters (user, job, reference, formtype, etc) the values different from *ALL and compare their values. '''Those which will have the more matching criterias with values different from *ALL will be executed.''' (Priority to the most selective rule). In the event where multiple rules have those same criterias, the first in the list will be taken and executed. | ||
| + | #: '''<u>NO MATCH</u>''' --> <span>The default rule ''' the rule with all criterias set to *ALL''' (if existing) will then be executed. (If not existing, a non visible error message in the MAPPING robot log will be risen and no action will be executed)</span> | ||
Version actuelle datée du 9 juin 2020 à 07:15
- The engine search first in the rules associated the full name of the spooled file.
- MATCH --> We look for the other parameters (user, job, reference, formtype, etc) the values different from *ALL and compare their values. Those which will have the more matching criterias with values different from *ALL will be executed. (Priority to the most selective rule). In the event where multiple rules have those same criterias, the first in the list will be taken and executed.
- NO MATCH --> Go to point 2
- The engine search in the rules associated another match with the other parameters (Please note that the partiel name has the same effect as the other parameters. Example : INV* for INVOICE. Indeed there is no priority on the partiel spooled file name) .
- MATCH --> We look for the other parameters (user, job, reference, formtype, etc) the values different from *ALL and compare their values. Those which will have the more matching criterias with values different from *ALL will be executed. (Priority to the most selective rule). In the event where multiple rules have those same criterias, the first in the list will be taken and executed.
- NO MATCH --> The default rule the rule with all criterias set to *ALL (if existing) will then be executed. (If not existing, a non visible error message in the MAPPING robot log will be risen and no action will be executed)