---
title: Inner Tree Evaluator node
description: Configure the Inner Tree Evaluator node to nest authentication journeys as children within a parent journey in PingAM.
component: platform
version: 7.5
page_id: platform:auth-node-ref:inner-tree-evaluator
canonical_url: https://docs.pingidentity.com/platform/7.5/auth-node-ref/inner-tree-evaluator.html
llms_txt: https://docs.pingidentity.com/platform/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-inner-tree-evaluator.adoc"]
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
  example: Example
---

# Inner Tree Evaluator node

The Inner Tree Evaluator node lets you nest authentication journeys as children within a parent. There is no limit to the depth of nesting.

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes        |
| Ping Identity Platform (self-managed) | Yes        |

## Inputs

Any information collected or set by the parent journey, such as a username or the authentication level, is available in the child journeys.

For information about shared state data, refer to [Access shared state data.](https://docs.pingidentity.com/pingam/7.5/am-scripting/scripting-api-node.html#scripting-api-node-nodeState)

## Dependencies

None.

## Configuration

| Property  | Usage                                                                                                            |
| --------- | ---------------------------------------------------------------------------------------------------------------- |
| Tree Name | Select or enter the name of the authentication journey to evaluate.You must set this value; there is no default. |

## Outputs

Shared node state data collected by child journeys is available to the parent when evaluation of the child is complete, but data stored in transient and secure state is not. For instance, if a child journey collects and stores the user's password in transient state, it cannot be retrieved by a node in the parent journey when evaluation continues.

For information about shared state data, refer to [Access shared state data.](https://docs.pingidentity.com/pingam/7.5/am-scripting/scripting-api-node.html#scripting-api-node-nodeState)

## Outcomes

* `True`

  Successfully reached the `Success` node of the child.

* `False`

  Any other case.

## Errors

If it cannot get the shared node state from the child, this node logs an `Exception when gathering inner tree inputs` message.

If the Tree Name doesn't match an existing journey, this node throws an exception with a `Configured tree does not exist: <tree-name>` message.

## Example

The following journey uses an [Inner Tree Evaluator node](inner-tree-evaluator.html) for progressive profiling:

![Login with progressive profiling](_images/call-inner-journey.png)

* The [Page node](page.html) presents a page with input fields to prompt for the username and password.

  * The [Platform Username node](platform-username.html) collects and injects the `userName` into the shared node state.

  * The [Platform Password node](platform-password.html) collects and injects the `password` into the shared node state.

* The [Data Store Decision node](data-store-decision.html) uses the username and password to determine whether authentication is successful.

* The [Increment Login Count node](increment-login-count.html) updates the login count on successful authentication.

* The [Inner Tree Evaluator node](inner-tree-evaluator.html) (outlined) invokes a nested journey:

![Progressive profiling journey](_images/inner-journey.png)

* The [Login Count Decision node](login-count-decision.html) triggers the rest of the journey depending on the login count and its settings.

* The [Query Filter Decision node](query-filter-decision.html) determines whether managed object profile fields are still missing.

* The [Attribute Collector node](attribute-collector.html) in the [Page node](page.html) requests additional input for the profile.

* The [Patch Object node](patch-object.html) stores the additional input in the managed object profile.