Component and script priorities
Component manifest files define two types of priorities:
The first one, in the component element itself, determines the order of loading of components.
Component dependencies are installed before the component that lists them as dependencies.
Where there are "tie-breakers" required (several components with the same dependencies affecting the same policies, but with no cross-dependencies between them), the component priority also determines the component evaluation order.
The higher the priority setting, the later it is evaluated, so the higher its actual priority in evaluating its function (for example attribute calculation).
The second type of priority is that for scripts running inside exit traps or plugin points.
That script priority, similarly with the component priority, determines the order of running several components which are defined for the same plugin point or exit trap.
The higher the priority number, the later the script is run compared to the other ones defined by other components for the same event.