From 02c5d99be08d959e951e84355dad73ca2e5ab644 Mon Sep 17 00:00:00 2001 From: Maarten de Kruijf Date: Fri, 2 Aug 2024 14:49:31 +0200 Subject: [PATCH] Updated playbook action step documentation --- docs/content/en/docs/core-components/executer.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/content/en/docs/core-components/executer.md b/docs/content/en/docs/core-components/executer.md index 0ccd56d5..52bf5567 100644 --- a/docs/content/en/docs/core-components/executer.md +++ b/docs/content/en/docs/core-components/executer.md @@ -174,7 +174,7 @@ end The playbook executor handles execution of playbook action steps. The variables from the top level playbook are injected into the be executed playbook. It could happen that in the downstream playbook the variables `collide` with the top level playbook. In this case the top level playbook variables are `NOT` transferred to the downstream playbook. `Agents and Targets cannot be transferred` between playbooks at this time. Playbooks are only loaded in the executor and then a new Decomposer is created to execute the playbook. -The result of the step execution will be returned to the decomposer. A result can be either output variables or error status. +The result of the step execution will be returned to the decomposer. A result can be either output variables or error status. Only variables defined in the out_args of the playbook action step will be merged into the global scope of the caller. ```plantuml package playbookaction{ @@ -194,6 +194,10 @@ database <- exe ``` +NOTE: in the future variables will be merged into the downstream playbook only if they are defined external on the downstream playbook. + + + ### If condition executor The if-condition executor will process a cacao if-condition step and determine it's output.