EMA C++ RDM Usage Guide : 6 Market Price Domain : 6.4 Special Semantics : 6.4.2 Ripple Fields
 
6.4.2 Ripple Fields
Some fields in a FieldList are defined as ripple fields. When the value of a ripple field changes, the former value automatically becomes the new value of another field. The change to the second field may, in turn, cause another field to be changed to reflect the second field’s former value. Whether or not fields are rippled is determined by the value of DoNotRipple.
When a refresh message is received, all of the ripple fields delivered by the Venue/Exchange are present in the refresh message. However, the consuming application must set ripple behavior for fields not in the refresh message. In some cases, the values delivered for the “ripple-to” Fields in the refresh may be empty, but they must be present.
It is a responsibility of the Consumer application to ripple the Fields. The Enterprise Message API does NOT ripple fields on behalf of the consumer application. The Open Message Model FieldList concept supports rippling. However, the FieldList class does not cache, so it cannot ripple fields.