]`.
+
+## Source Records and How Anomalies Render
+
+When you open the source records for an Expected Values anomaly, the platform highlights **only the offending cell** for the field the check applies to. Other columns in the same row are rendered normally. This matches how the check semantics work: the violation is about a single field's value, not the entire row.
+
+The Sample Data tables on the [Examples](examples.md){:target="_blank"} page follow the same convention: one row per source record, with only the failing cell visually marked.
+
+## Relationship with Other Rule Types
+
+The Expected Values check is most powerful when used together with a small set of complementary rule types:
+
+| Rule Type | Why pair it with Expected Values |
+|:---|:---|
+| [Not Null](../not-null-check.md){:target="_blank"} | Expected Values lets NULLs pass. Pair with Not Null on the same field when missing values are also a violation. |
+| [Required Values](../required-values-check.md){:target="_blank"} | Expected Values asserts that values come **from** a list (subset). Required Values asserts that the field contains **at least** the values in a list (superset). They are mirror images: use both when the column must contain every required value *and* nothing outside the vocabulary. |
+| [Matches Pattern](../matches-pattern-check.md){:target="_blank"} | Use Matches Pattern when the accepted values follow a regular structure rather than a finite list (for example, `SKU-\d{4}`). Expected Values is the right tool when the vocabulary is small and enumerable. |
+| [Satisfies Expression](../satisfies-expression-check.md){:target="_blank"} | Use a custom Spark SQL expression when you need case-insensitive matching (`lower(field) IN ('o', 'f', 'p')`) or any other normalization Expected Values does not perform natively. |
+
+The Expected Values check can also be created automatically as an **AI Managed check** when a Profile operation detects that a column has a small, stable set of distinct values. See the [AI Managed Checks Introduction](../ai-managed/introduction.md){:target="_blank"} for how AI Managed checks are generated and how editing one converts it to Authored.
diff --git a/docs/data-quality-checks/expected-values/introduction.md b/docs/data-quality-checks/expected-values/introduction.md
new file mode 100644
index 0000000000..bdf13a0592
--- /dev/null
+++ b/docs/data-quality-checks/expected-values/introduction.md
@@ -0,0 +1,101 @@
+# Expected Values Check
+
+## Definition
+
+*Asserts that the value in the selected field is contained in a predefined list of accepted values.*
+
+## Overview
+
+The Expected Values rule enforces a closed vocabulary on a single column. The check compares each row's value against a list configured on the rule and flags every row whose value is not in the list. Typical use cases include:
+
+- Enforcing status enums (`order_status`, `payment_state`).
+- Restricting a country, currency, or locale code to an allowed set.
+- Validating short categorical fields (`tier`, `channel`, `segment`).
+- Asserting that an array column contains only elements from a known vocabulary.
+
+NULL values pass the check. The rule only evaluates non-NULL values against the list, so an Expected Values check on a nullable field never fires on missing values. Pair it with a [Not Null](../not-null-check.md){:target="_blank"} check on the same field when missingness is also a violation.
+
+## Field Scope
+
+**Single:** The rule evaluates one field per check.
+
+**Accepted Types**
+
+| Type | Supported |
+|-------------|:------------------------:|
+| `Date` | :material-check-circle:{ style="color: #4caf50" }
|
+| `Timestamp` | :material-check-circle:{ style="color: #4caf50" }
|
+| `Integral` | :material-check-circle:{ style="color: #4caf50" }
|
+| `Fractional`| :material-check-circle:{ style="color: #4caf50" }
|
+| `String` | :material-check-circle:{ style="color: #4caf50" }
|
+| `Boolean` | :material-check-circle:{ style="color: #4caf50" }
|
+
+For `Date` and `Timestamp`, the list is compared as strings against the column's rendered value. See [How It Works](how-it-works.md){:target="_blank"} for details and recommended formats.
+
+## General Properties
+
+{%
+ include-markdown "components/general-props/index.md"
+ start=''
+ end=''
+%}
+
+## Specific Properties
+
+Specify the predefined list of values that the field is allowed to contain.
+
+| Name | Description |
+|:---|:---|
+| List
| The predefined set of accepted values. Every non-NULL value in the selected field must match one of these entries exactly (case-sensitive, no whitespace trimming). |
+
+{%
+ include-markdown "components/general-props/warning.md"
+ start=''
+ end=''
+%}
+
+## Anomaly Types
+
+{%
+ include-markdown "components/anomaly-support/index.md"
+ start=''
+ end=''
+%}
+
+## Next Steps
+
+
+
+- **How It Works**
+
+ ---
+
+ Full semantics on NULL handling, type coercion, array support, filter and coverage behavior, and resulting anomalies.
+
+ [:octicons-arrow-right-24: How It Works](how-it-works.md)
+
+- **Examples**
+
+ ---
+
+ Three production scenarios with sample data, anomaly messages, and the equivalent SQL the check evaluates.
+
+ [:octicons-arrow-right-24: Examples](examples.md)
+
+- **API**
+
+ ---
+
+ Payload shape and field notes for creating an Expected Values check programmatically.
+
+ [:octicons-arrow-right-24: API](api.md)
+
+- **FAQ**
+
+ ---
+
+ Short answers to questions about case-sensitivity, NULL handling, array support, and anomaly reporting.
+
+ [:octicons-arrow-right-24: FAQ](faq.md)
+
+
diff --git a/docs/data-quality-checks/overview-of-a-check.md b/docs/data-quality-checks/overview-of-a-check.md
index faf8627146..f55e45dae2 100644
--- a/docs/data-quality-checks/overview-of-a-check.md
+++ b/docs/data-quality-checks/overview-of-a-check.md
@@ -173,7 +173,7 @@ For more details about check rule types, please refer to the [**Rule Types Overv
| [Equal To Field](../data-quality-checks/equal-to-field-check.md) | Asserts that this field is equal to another field. |
| [Exists in](../data-quality-checks/exists-in-check.md) | Asserts if the rows of a compared table/field of a specific Datastore exists in the selected table/field.|
| [Expected Schema](../data-quality-checks/expected-schema-check.md) | Asserts that all selected fields are present and that all declared data types match expectations. |
-| [Expected Values](../data-quality-checks/expected-values-check.md) | Asserts that values are contained within a list of expected values. |
+| [Expected Values](../data-quality-checks/expected-values/introduction.md) | Asserts that values are contained within a list of expected values. |
| [Field Count](../data-quality-checks/field-count-check.md) | Asserts that there must be exactly a specified number of fields. |
| [Freshness Check](../data-quality-checks/freshness-check.md) | Asserts that data was added or updated in the data asset after a declared time. |
| [Greater Than](../data-quality-checks/greater-than-check.md) | Asserts that the field is a number greater than (or equal to) a value. |
diff --git a/docs/data-quality-checks/rule-types-overview.md b/docs/data-quality-checks/rule-types-overview.md
index 7f08905007..6777384888 100644
--- a/docs/data-quality-checks/rule-types-overview.md
+++ b/docs/data-quality-checks/rule-types-overview.md
@@ -24,7 +24,7 @@ Here’s an overview of the rule types and their purposes:
| [Equal To Field](../data-quality-checks/equal-to-field-check.md) | Asserts that this field is equal to another field. |
| [Exists in](../data-quality-checks/exists-in-check.md) | Asserts if the rows of a compared table/field of a specific Datastore exists in the selected table/field.|
| [Expected Schema](../data-quality-checks/expected-schema-check.md) | Asserts that all selected fields are present and that all declared data types match expectations. |
-| [Expected Values](../data-quality-checks/expected-values-check.md) | Asserts that values are contained within a list of expected values. |
+| [Expected Values](../data-quality-checks/expected-values/introduction.md) | Asserts that values are contained within a list of expected values. |
| [Field Count](../data-quality-checks/field-count-check.md) | Asserts that there must be exactly a specified number of fields. |
| [Greater Than](../data-quality-checks/greater-than-check.md) | Asserts that the field is a number greater than (or equal to) a value. |
| [Greater Than Field](../data-quality-checks/greater-than-field-check.md) | Asserts that this field is greater than another field. |
diff --git a/docs/stylesheets/extra.css b/docs/stylesheets/extra.css
index acec27b991..fd9dbbf20d 100644
--- a/docs/stylesheets/extra.css
+++ b/docs/stylesheets/extra.css
@@ -241,6 +241,7 @@
--q-negative: #E91E63;
--q-warning: #ffbb33;
--q-orange: #F96719;
+ --q-orange-rgb: 249, 103, 25;
--q-invalid: #5A678F;
/* MkDocs Variables */
@@ -558,6 +559,7 @@
--q-negative: #E91E63;
--q-warning: #ffbb33;
--q-orange: #F96719;
+ --q-orange-rgb: 249, 103, 25;
--q-invalid: #828db0;
/* MkDocs Variables */
@@ -955,6 +957,19 @@
color: var(--q-brick);
}
+/* Inspired by the source-records anomalous-cell treatment in the Qualytics app:
+ orange outline plus a warning-tinted background on cells whose value failed a check.
+ Use inside markdown table cells to mark a single value as anomalous. */
+.anomalous-cell {
+ display: inline-block;
+ padding: 0.05rem 0.4rem;
+ border: 1px solid var(--q-orange);
+ border-radius: 4px;
+ background-color: rgba(var(--q-orange-rgb), 0.12);
+ color: var(--q-brick);
+ font-weight: 500;
+}
+
.text-sm {
font-size: 0.7rem;
}
diff --git a/mkdocs.yml b/mkdocs.yml
index 649473ca96..bd34c5446a 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -319,7 +319,12 @@ nav:
- Equal to Field: data-quality-checks/equal-to-field-check.md
- Exists In: data-quality-checks/exists-in-check.md
- Expected Schema: data-quality-checks/expected-schema-check.md
- - Expected Values: data-quality-checks/expected-values-check.md
+ - Expected Values:
+ - Introduction: data-quality-checks/expected-values/introduction.md
+ - How It Works: data-quality-checks/expected-values/how-it-works.md
+ - Examples: data-quality-checks/expected-values/examples.md
+ - API: data-quality-checks/expected-values/api.md
+ - FAQ: data-quality-checks/expected-values/faq.md
- Field Count: data-quality-checks/field-count-check.md
- Freshness Checks: data-quality-checks/freshness-check.md
- Greater Than: data-quality-checks/greater-than-check.md
@@ -1167,7 +1172,8 @@ plugins:
'checks/equal-to-field-check.md': 'data-quality-checks/equal-to-field-check.md'
'checks/exists-in-check.md': 'data-quality-checks/exists-in-check.md'
'checks/expected-schema-check.md': 'data-quality-checks/expected-schema-check.md'
- 'checks/expected-values-check.md': 'data-quality-checks/expected-values-check.md'
+ 'checks/expected-values-check.md': 'data-quality-checks/expected-values/introduction.md'
+ 'data-quality-checks/expected-values-check.md': 'data-quality-checks/expected-values/introduction.md'
'checks/field-count-check.md': 'data-quality-checks/field-count-check.md'
'checks/freshness-check.md': 'data-quality-checks/freshness-check.md'
'checks/greater-than-check.md': 'data-quality-checks/greater-than-check.md'