Escalation Condition

The Escalation Condition object contains the condition which is used for the Condition Escalation. This Condition is applied to the object referred to in the Object Type attribute in the Escalation Type object. If the condition is met then the Actions are carried out.

Help Image

The Catalog of Escalation Conditions

There could be several Conditions to an Escalation TypeLevel – they are differentiated by a running number. The conditions are tested in ascending order.

Help Image

Escalation Conditions

The Condition Escalation contains the following attributes:

Window Component	Function / Meaning
Running number	A number to differentiate between a number of conditions which may be associated with an Escalation TypeLevel.
Negative	Escalation Actions will be executed if no object meets the given condition.
Step by step	This setting is valid only if the "Negative" is not set to 'true'. If checked, the subworkflow is called for each object in the result collection and the parameter "bo" is passed to the subworkflow. If unchecked, the complete result collection with the parameter named "bos" is passed to the subworklfow.
Read Increment	The number of objects that will be read in one batch. The recommended value is 100-400. If the value is empty, all objects matching the condition will be read at the beginning, which may result in performance issues.
Commit Limit	The number of objects that need to be processed before the changes will be committed to the database. The recommended value is 10-400. If this value is empty, changes will be committed after each step, which may result in performance issues.
Contents	The actual condition. The parenthesis are used in the same way but symbol “\|\|” is used for logical OR, symbol “&&” is used for logical AND and symbol “==” is used for Equals. The names used for Attributes and Objects are those from the BO Customizer and not the Database attribute names.
Escalation TypeLevel	The Escalation TypeLevel for which this condition applies.