Users may consider an example where the Job prioritization map for a specific project has the following prioritization map entries:
Users may expect that all reports (whether scheduled or regular interactive execution) for group "X" would be executed with a HIGH job priority against the warehouse, and all other scheduled report executions would execute with a MEDIUM priority.
The Intelligence Server behavior however is slightly different from the expected behavior detailed above. To determine job priorities, the Intelligence Server reads the project job prioritization map and determines how many "factors" to match each map entry contains (the ALL value does not count as a specific match factor). When a job is run, the job parameters are matched against the priority factors, and the priority associated with the prioritization entry matching the maximum number of factors is used for the job.
For the example above, a scheduled report run by the user of group "X" would run with a priority MEDIUM and not HIGH. This is because the job would match two factors - request type:REPORTS and application type:SCHEDULER.
This behavior of the Intelligence Server is designed to be a similar implementation to other Strategy settings, where report level settings can override project level settings. In this implementation, the priority associated with job prioritization map entries for detailed matching factors will override the more generic (less specific) map entries.
To make all scheduled and interactive jobs for group "X" run with a high priority, the following priority map entries would need to be defined. This will cause the scheduled report jobs for group "X" to also run with a HIGH priority.
