From 1c7bb16f5901f1f9ad1f07448155295bc36e30f6 Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Mon, 21 May 2018 13:53:56 +0100 Subject: [PATCH] Updated Design: Using environment variables (markdown) --- Design:-Using-environment-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Design:-Using-environment-variables.md b/Design:-Using-environment-variables.md index b899947..2010fde 100644 --- a/Design:-Using-environment-variables.md +++ b/Design:-Using-environment-variables.md @@ -62,7 +62,7 @@ Both the Project Settings and Subflow Instance properties list would also suppor This does mean compound env vars would only be possible using these new features - not in any arbitrary node property ``. But a compound env var could be declared in Project Settings of Subflow Instance Properties which is then available as a simple `${NEW_ENV_VAR}` to use anywhere in the flow. -5. JSONata support for env vars +### 5. JSONata support for env vars We'll add a new function to our JSONata setup to allow env vars to be retrieved: