...
So, to validate, we need to create/copy an existing Test Case, and set the From: address to be boss@localhost:
...
, Submit to save
Now run the Test Case:
Analysing the result
The result screen shows:
1.The Profile that was used
2.The Project Mapping that was used
3.The Rule that matched
4.The value that caused the match
The important thing here is what Rule applied, (3) above shows .*@localhost which is a general match for <anyone>@localhost. It won because that rule had a default priority, and the other rule for boss@localhost also had that priority, ie, it was no better.
Updating the Boss rule
Now change the boss rule to have a have a priority value other than default, note that the Project Mapping view gives short cut edit links to each rule, use it for RULE 2:
Setting any priority will result in a win over a default priority Rule so, set the lowest possible (20), and Submit:
Now see the priority in the Rule:
Repeating the Test Case execution above, this time, the results are different, below, you can see that the modified Rule (1) has been matched on the sender address value (2). All customizations relating to the issue would then have been applied:
Performance Considerations
To make best use of resources, JEMHC loads all rules and sorts them in priority, order, this means that the highest rules will be tested first. Once a rule match wins, equal or lower priority rules are discarded.
Related articles
| Filter by label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...