From e89b2a0f07627dbf3bffd02a3f096cdb64dfad7b Mon Sep 17 00:00:00 2001 From: Siddhant Dua Date: Wed, 10 Sep 2025 11:46:34 +0530 Subject: [PATCH] Added step group expressions in docs --- .../x-platform-cd-features/cd-steps/step-groups.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/continuous-delivery/x-platform-cd-features/cd-steps/step-groups.md b/docs/continuous-delivery/x-platform-cd-features/cd-steps/step-groups.md index f9c2abe017d..7291d612ea0 100644 --- a/docs/continuous-delivery/x-platform-cd-features/cd-steps/step-groups.md +++ b/docs/continuous-delivery/x-platform-cd-features/cd-steps/step-groups.md @@ -92,11 +92,17 @@ If you are accessing the output variable in a step within the same step group yo If your step group is configured as a loop, an index is added at the end of the identifier to identify the unique loop instance. You can use this index to reference output variables. For example, `<+execution.steps..steps.stepID.outputVariables.[variable name]>`. - :::info Execution input is not supported for step group variables. ::: +## Step group expressions + +The following expressions are for step groups in pipeline stages. + +* `<+stepGroup.variables>`: References a collection of variables within the step group. +* `<+stepGroup.getParentStepGroup>`: References a collection of variables from the parent of the step group. + ## Conditional execution A step group can have its own conditional execution settings separate from the conditional execution settings for the stage. The conditional execution settings of the step group apply to all of its steps.