Static Versus Dynamic Candidates
When processing rules, Assignment Manager determines potential candidates either statically or dynamically. Assignment Manager determines candidates statically in these cases:
When candidates are explicitly added to an assignment rule.
When the All People or All Organizations flags are checked on an assignment rule.
When qualifying candidates based on their skills.
Static candidates do not change as Assignment Manager processes rules (unless you intentionally associate other, different candidates) whereas dynamic candidates are identified during assignment.
Dynamic candidates can come from different, but related business entities. For example, Assignment Manager can assign an activity related to an asset and then dynamically generate a candidate list from the asset team.
Assignment Manager determines dynamic candidates as potential assignees for objects from an attribute on the object row. For example, assume that you have an activity that is associated to an asset. The asset, in turn, is associated with a list of employees. You might want Assignment Manager to treat the list of employees associated with the asset as potential candidates for assignment of that activity. In this situation, the potential candidates are dynamic candidates because they are not statically associated with an assignment rule; instead, they are identified during assignment.
Also note that, if the activity is later associated with a different asset that is associated with a different set of employees, then the list of potential candidates for the same activity can change during the next assignment.
In summary, the following points explain how static candidate assignment differs from dynamic candidate assignment:
For static candidate assignment, candidates for each assignment rule are loaded when the server processes start up.
For dynamic candidate assignment, candidates are retrieved from related business entities (attribute team table) with respect to the object row during an assignment.