'Changes' operator
This table shows the syntax for rules that use the 'Changes' operator:
Syntax | [Attribute] [Operator] [optional Condition] |
---|---|
Attribute | One of the document attributes selected for monitoring. |
Operator | Changes |
Condition (optional) | A monitor condition from the list of predefined conditions. |
Evaluation if Operator = Changes | Evaluates to true if an instance of the document was received followed by a new instance of the same document, with a different value than the previous one.
If a Condition is specified, only the document instances for which the Condition evaluates to True are considered for evaluation. |
This table shows when alerts are generated:
Document instances | Alert is generated |
---|---|
First document instance contains the Attribute with any value. | No |
Two document instances follow each other, each having a different value for the Attribute. | Yes |
Two document instances follow each other, both having the same value for the Attribute. | No |
Note: If several document instances are received with the same CreationDateTime, but different values for the Attribute, only one of the document instances is used in the evaluation. No alert is generated until a new document instance with a different CreationDateTime and a different attribute value is received.
Example - Changes
You can make changes to a planned Shipment. For example, another carrier is assigned. If this is a change to be alerted on, you can create a rule to monitor value changes on the carrier party from the Shipment document.
This table shows the syntax of the rule:
Attribute | CarrierParty |
---|---|
Old Value | N/a |
Operator | Changes |
New Value | N/a |
Within | N/a |