Referential Integrity Rules and Cardinality Rules replaced by improvements in Validation Monitors

Up until this week, Cardinality Rules and Referential Integrity Rules were options on the Monitor Menu in Monte Carlo. These were purpose-built monitor creation experiences that produced a SQL Rule. These were for use cases like:

Alert me if any of the values in [field] are not included in set [value1, value2, value3, etc]
Alert me if any of the values in [field] are not present in [table > field]

Existing Cardinality Rules and Referential Integrity Rules will continue to run normally. But the workflows to create these have now been removed from the monitor menu.

Referential Integrity Rules and Cardinality Rules were made redundant by new ways to define a set in Validation Monitors. In Validation Monitors, the recommended way to address these use cases in now with the Is in set and Is not in set operators, which allow a user to define a set:

From a list: manually enter the values
From a field: select a table and field, and the set with be populated with the distinct values in that field. The selected field will be referenced each time the monitor is run, so the set values may change.
From a query: write SQL to define the values in the set. The query will run each time the monitor is run, so the set values may change.