> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-value-from-global-context.md).

# Get Value from Global Context

## Description

Located in process nodes in the *Data objects* dropdown menu, the *Get value from global ctx* part allows you to access a variable in the global context when the system performs processing in a different local context.

## Use

This part is most often used when using the Repeating Inputs within the LogicNets Assessment Framework. If the user sets a value in the main application that is required for a rule or processing step in the repeated section, use this part to "get" the global variable and include it in the collection generated by the repeater.

## Tips and Tricks

If your repeating logicnet model just needs some information from the main application temporarily, then you can do the following:

* Copy the full path of the main variable from the global context.
* Rename it to a short/simple name for the local context. The system shows it as part of the repeater collection set.
* Set a *delete object* part at the end of the repeating logicnet, which is not the main application. The system will remove the variable/container from the collection and keep the size of the overall context down. If you do not do this, the system adds the variable to EVERY collection record in the repeater. You can see this if you inspect the context using the DATA button.

Make sure you place this part BEFORE the local logic that requires the information, but in the same logicnet. This should not go in the same logicnet containing the call node to the repeating/local logicnet.

## Editor Fields

| Field Name                        | Description/Use                                                                              | Type/Options                    | Optional/Mandatory |
| --------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------- | ------------------ |
| Target data object in current ctx | This specifies the name of the variable in the current context                               | <p>Data Object<br>Container</p> | Mandatory          |
| Source data object in global ctx  | This is the name of the object in the global context that is required in the current context | <p>Data Object<br>Container</p> | Mandatory          |

## Example

Download and import the following example project in your workspace. COMING SOON!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/get-value-from-global-context.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.