From 3d5090d49dc7e8165103f49cb58ac08666d797bb Mon Sep 17 00:00:00 2001 From: dc Date: Tue, 20 Oct 2026 09:01:58 +0000 Subject: [PATCH] docs(config): validation rules on MPE_DERIVED --- docs/derived-variables.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/derived-variables.md b/docs/derived-variables.md index bdc2cb4..1f6fe51 100644 --- a/docs/derived-variables.md +++ b/docs/derived-variables.md @@ -80,6 +80,8 @@ A configuration error - a bad name, an invalid type or length, a name collision, Most of these rules are also applied when a row is submitted for approval, through a post edit hook on `MPE_DERIVED`. A bad name, type, length, format or expression - or a duplicate name, or a reference to a variable that is not defined earlier - is rejected at submit time, while the error can still be corrected, rather than breaking the EDIT screen afterwards. The collision between `VAR_NM` and a physical column of the target table is only checked at read time, as the hook does not have the target library assigned. +The simple rules are also configured as validation rules on the table itself, so they show up in the grid before submission: `VAR_TYPE` is a dropdown of `C` and `N`, `VAR_ORDER` and `VAR_LEN` carry minimum and maximum values, and `VAR_NM`, `VAR_FMT` and `VAR_LOGIC` are pattern checked. Validation rules are evaluated in the browser, so the post edit hook remains the authoritative check. + !!! warning "Derived values can expose hidden data" An expression can reference a column that is hidden from the user by [Column Level Security](/column-level-security/), and the derived column will show the result. Configure derived variables with the same care as any other data exposure.