The 'becomes' setting

The 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.

ConditionEventOld valueNew ValueCondition met if becomes=offCondition met if becomes=on
itemGroup = "X"create-XYesYes
create-YNoNo
deleteX-YesNo
deleteY-NoNo
changeXXYesNo
changeXYNo (!)No
changeYXYesYes
changeYYNoNo
quantity = 0create-0YesYes (!)
create-1NoNo
delete0-YesNo
delete1-No (!)No (!)
change00YesNo
change01No (!)No
change10YesYes
change11NoNo
quantity <> 0create-1YesYes
create-0NoNo
delete1-YesNo
delete0-NoNo (!)
change11YesNo
change10No (!)No
change01YesYes
change00NoNo
quantity changedcreate-1Yes-
create-0Yes-
delete1-Yes-
delete0-Yes-
change11No-
change10Yes-
change01Yes-
change00No-

 

Note

Unlike in other products such as the Synchronization Server, a condition won't change the event type from 'change' to 'create' or 'delete'.