1. Create a parameter in the child playbook.

2. Apply the parameter to the Disable User Account connector action.

3. Map data to the parameter in the Reference a playbook step in the parent playbook.

Comprehensive and Detailed Explanation From FortiSOAR 7.6., FortiSIEM 7.3 Exact Extract study guide:

InFortiSOAR 7.6, the methodology for passing data between playbooks—specifically from a parent to a "Referenced" (child) playbook—follows a strict data flow hierarchy:

Step 1: Create a parameter in the child playbook.Before a parent can send data, the child playbook must be configured to receive it. This is done by adding "Input Parameters" in theStartstep of the child playbook (configured as a "Referenced" trigger). These parameters act as the "inbox" for external data.

Step 2: Apply the parameter to the connector action.Once the child playbook has the parameter defined (e.g., user_id), you must use a Jinja expression like {{vars.input.params.user_id}} within the child's action steps (such as theActive Directory: Disable User Accountconnector) so that the child playbook actually utilizes the data it receives.

Step 3: Map data to the parameter in the parent playbook.Finally, in the parent playbook, when you add theReference a Playbookstep and select the child playbook, FortiSOAR automatically displays the parameters created in Step 1. You then map existing variables from the parent's environment (e.g., from a previous "Search by SamAccountName" step) into these fields to complete the hand-off.

Why other options are excluded:

Create a manual trigger and assign the user to a new variable:While manual triggers capture data, they are not the mechanism forpassingdata between nested playbooks; they are for user-to-system interaction.

Create a parameter in the parent playbook:Parameters in a parent playbook are used to receive data fromoutside(like an external API or manual input), not to send datadownto a child. The child defines what it needs; the parent simply provides it in the Reference step.