Delay rules define which events should be delayed and what conditions trigger their release. Multiple delay rules are allowed.
The following delay rules available:
Number of events rule.
This rule specifies the minimum number of events that need to be delayed in order to release them for processing.
Specific event rule.
This rule states that B2B Data Exchange should delay all events until a specific event arrives which meets a condition set in the rule. An example of such a special event is one with an attribute set to a specific value, for example, an event whose EndofDay attribute is True.
Combination rule.
There are several variations of the definition of the combination rule.
The first one is to delay all events until a threshold number of events has been delayed, for example, delay 900 events. This rule is similar to the Number of Events rule.
The second variation of the combination rule is to delay all events until the accumulated total of an event attribute reaches an operator configurable value - for example, total price equals a threshold value.
The third variation of the combination rule is optional, and can be combined with one of the first two variations. This rule allows the operator to define which events are accumulated. Events are identified by an event attribute that holds a specific value, for example, delay 100 events whose PartnerCode attribute is 147, or delay all events whose PartnerCode attribute is 147, until their Total price equals 10,000.
By-event rule.
This rule is used to re-group events. The rule groups events by an operator-selected event attribute. The size of the groups can be specified by another event attribute.