When a Type is defined, a Default Processor Group is associated with the Type.
For example, in this case, say BIND is the default Processor Group for Type BIND.
When a Type BIND element is added for the very first time, the programmer can use the default Processor Group defined in the Type Definition - BIND, or they can manually specify a different the Processor Group to use for that specific element, in this case BINDRUN.
Once this Processor Group association is made, Endevor remembers which Processor Group was specified for that element and uses that Processor Group from then on when processing Add, Update, Move, Generate, Delete, or Transfer actions for that element.
The Processor Group can be changed by specifying a new Processor Group during an Add/Update or Transfer of the element.