> 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/form-node-parts/advice.md).

# Advice

## Description

The *Advice* part allows you to display advice or descriptive text to the end user.

## Use

This part is available for those applications using the Visual Guidelines Framework. It allows you to display advice or descriptive text to the end user; for example, the text displayed could include a diagnostic conclusion or a recommendation for a specific order or next step.

## Editor Fields

| Field Name    | Description/Use                                                                                                                                                                                                                                                | Type/Options | Optional/Mandatory |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Label         | This field contains the text the system displays as the advice header.                                                                                                                                                                                         | Text         | Mandatory          |
| Path          | This field contains text that can be used to look up additional information.                                                                                                                                                                                   | Text         | Optional           |
| Call logicnet | This field holds the id of the logicnet to be called for additional information or selection options. If you use this field the UI will display a circle a circle with a dropdown arrow. When a user clicks the icon the system opens the identified logicnet. | Text         | Optional           |
| Description   | This field holds the descriptive text or advice the system will display when the end user reaches the node.                                                                                                                                                    | Text         | Mandatory          |

## Example

There are different types of advice nodes that can be displayed to end users. The first is a simple advice node, which contains descriptive text. The second type of advice node contains a call icon, which allows the end user to see additional information or selection options.

1\. Simple Advice Node

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-97ab55f84d7f932b3764c3162872b1b92ee33af4%2Fc64017c8-a3c3-44c5-becf-f4547b17dc60.png?alt=media)

2\. Advice Node with Call Icon

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0422560b3e0bca70be10cf93bf8a0c140ae7d602%2F1a2296fc-0830-42e8-9a6f-f49135635b02.png?alt=media)


---

# 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/form-node-parts/advice.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.