|
|
A new client parameter determines how triggers are executed and how they are logged in the system. The STRICTMODEONFORFIRINGTRIGGERS parameter is enabled by default and sets trigger execution to strict mode. In strict mode, users are only be able to fire triggers in the order that they were logged for each candidate profile. If a user attempts to move a candidate while there are pending triggers associated with that profile, the triggers are queued and the user receives a confirmation message. On the Queued Triggers/All Triggers and the Candidate Trigger Log History tables, only the first actionable trigger can be fired. All later triggers will have the action button disabled until all previous triggers are fired.
When this parameter is disabled, the triggers are no longer in strict mode and work as they always have. A user can drag a candidate into a folder and fire triggers regardless if there are actionable triggers in the log. On the Queued Triggers/All Triggers and the Candidate Trigger Log History tables, users can fire the first actionable trigger for each respective move. For more information on managing client parameters, see About Client Parameters.
Additional Information
|
|
