| The 'becomes' settingThe following table shows how the 'Becomes' setting
works. The table below contains some exclamation marks for situations
where the behavior may not be obvious at first sight. - Regarding 'change' events, when an attribute value is changed
from a value that meets the condition to a value that doesn't meet the
condition, the change event is not processed.
- Regarding 'create' and 'delete' events, take into account that
attribute values that are missing do not have the same meaning as attributes
having an empty value, such as "" or 0. So if an entity is deleted, that
doesn't mean that the attribute value for that entity becomes 0, because it is
undefined.
If specific handling of these situations is needed, you can
combine conditions on attribute values with conditions on event
type. Condition | Event | Old
value | New Value | Condition met if becomes=off | Condition
met if becomes=on | itemGroup =
"X" | create | - | X | Yes | Yes | | create | - | Y | No | No | | delete | X | - | Yes | No | | delete | Y | - | No | No | | change | X | X | Yes | No | | change | X | Y | No (!) | No | | change | Y | X | Yes | Yes | | change | Y | Y | No | No | | | | | | | quantity
= 0 | create | - | 0 | Yes | Yes
(!) | | create | - | 1 | No | No | | delete | 0 | - | Yes | No | | delete | 1 | - | No (!) | No (!) | | change | 0 | 0 | Yes | No | | change | 0 | 1 | No (!) | No | | change | 1 | 0 | Yes | Yes | | change | 1 | 1 | No | No | | | | | | | quantity
<> 0 | create | - | 1 | Yes | Yes | | create | - | 0 | No | No | | delete | 1 | - | Yes | No | | delete | 0 | - | No | No (!) | | change | 1 | 1 | Yes | No | | change | 1 | 0 | No (!) | No | | change | 0 | 1 | Yes | Yes | | change | 0 | 0 | No | No | | | | | | | quantity
changed | create | - | 1 | Yes | - | | create | - | 0 | Yes | - | | delete | 1 | - | Yes | - | | delete | 0 | - | Yes | - | | change | 1 | 1 | No | - | | change | 1 | 0 | Yes | - | | change | 0 | 1 | Yes | - | | change | 0 | 0 | No | - |
Note Unlike in other products such as the Synchronization Server, a
condition won't change the event type from 'change' to 'create' or 'delete'. | |