From 97d709a0616858128789b58ecdedd4543a39c82a Mon Sep 17 00:00:00 2001 From: Allan Bowe Date: Mon, 6 Sep 2021 21:29:03 +0300 Subject: [PATCH] chore: automated commit --- docs/dcc-validations.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/dcc-validations.md b/docs/dcc-validations.md index d6f8cd0..fe70c48 100644 --- a/docs/dcc-validations.md +++ b/docs/dcc-validations.md @@ -42,6 +42,8 @@ Further details on the above: These validations enable you to present a dynamic dropdown to the user based on other values in the same **row**. You can also use the response to populate _other_ dropdowns (also in the same row) in the same request - these are called 'extended validations'. + + Your hook script can be either a SAS program on the filesystem (in which case it must end with ".sas") or it can also be a Stored Process or Viya Job in the logical folder tree (metadata or SAS Drive) - in which case it must _not_ end with ".sas". In both cases you should provide the full path and filename in the MPE_VALIDATIONS table. For examples of hook scripts you can look at the Data Controller internal validation programs. In summary, you will receive the following as inputs: