> 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-application-details.md).

# Get Application Details

## Description

Using this part, the system returns the details of the application, including the package name, category, version, and settings of the application. When an application is based on a framework the system returns the application details and not the framework details, even when you use this part in the framework.

**Node Type:** This part is located in the *Misc* dropdown menu in the Process node.

**Used With:** You can use this part with all framework and non-framework projects.

## Editor Fields

Configure this part with the following fields:

| Field Name  | Description/Use                                                                 | Type/Option | Optional/Mandatory |
| ----------- | ------------------------------------------------------------------------------- | ----------- | ------------------ |
| Data-Object | This is the path to the object where the system writes the application details. | Object      | Mandatory          |


---

# 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-application-details.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.