| Table of Contents |
|---|
Summary
Within a JEMHC Profile you are able to create multiple Project Mappings which allow you to use one Profile for multiple Projects. This uses Rules to determine the Project Mapping that the Email should be processed with. Rules can only be used for non default Project Mappings as the Default Project Mapping is used when there has been no rule match for that email.
Default Project Mapping
| Info |
|---|
Changing values within the Default Project Mapping can affect the other Project Mappings if values are inherited. |
Default Project mappings are used when there has been no rule match for that email, this way is to ensure that the email will is still be being processed (unless inhibited by other factors). Non Default Project Mappings can inherit values from the Default Project mapping. This is to ensure that the configuration will process the emails correctly.
Non-Default Project Mappings
Non-Default Project Mappings use rules to determine which Project Mapping should be used to process that email. When this occurs the value will have a Inherited tag Each project Mapping can have multiple rules. For more information about rules see: Rules configuration
When Non-Default Project Mappings are created they will inherit most of it’s values from the Default Project Mapping. This is to assist with the configuration as there may only be small changes between the default and Non-Default Project Mappings.
When values are inherited it will have an Inherited tag next to the value as seen below:
...