EAR Algorithm

Following is the sequence of processes in the EAR algorithm:

For the Rule Group = EAR and for each Rule Set available, the application will process:

1. Each License Rule under Rule Category = License.
2. Assign the license with major precedence, if more than one, at the Rule Category = License level.
3. License Exception under Rule Category = Exception until finding an exception.
4. Assign the exception found to the Rule Category = Exception level.
5. Assign the license and exception (if any) coming from Rule Category level at the Rule Set level.
6. Process rule sets according to the setup done at the Rule Group level for each rule set. The following values given to the Rule Group will be considered to move to the next rule set and whether to consider the results of the current rule set as final:
   1. License Override Type
   2. Exception Override Type
   3. Is Exception on Restriction

 The following figure indicates a summary of the potential results at the end of each one of the processes:

A status will be assigned to the EAR Rule Group. It could be:

1. On Hold: when the result after processing all the Rule Sets is a license and no exception is available.
2. Released: When the result after processing all the Rule Sets is a license and an exception or there has not been any rule match for any Rule Set.

A status will be assigned to a Policy. It could be:

1. On Hold: when at least one Policy Template Status is On Hold
2. Released: When there is a license and exception or when there is no license rules match for any Rule Groups.