> 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/design-considerations-and-frameworks/frameworks/support-center-framework/customize-your-cause-selection.md).

# Customize Your Cause Selection

You can customize the cause selection popup using your own logicnets. To do this, the system offers the following data objects for populating your own custom cause-selection popup:

* *\_scfw\.selected\_causes* (aka fingerprints) – This holds the array of the selected causes for the troubleshooting logicnets. The 'selection\_key' is the reference to the unique name of the troubleshooter logicnet. You can extend the selected\_cause with custom data objects for exporting to the Starter Application.
* *\_scfw\.end\_points* – This holds the array of conclusions of the "currently active" troubleshooting logicnet. The system groups reachable end points under \_scfw\.end\_points.inclusions. Non-reachable end\_points are grouped under \_scfw\.end\_points.exclusions.
* *\_scfw\.select\_cause.action* – This is where the system stores the action with which the popup is stepped. Typically, you must use this data object for the "Confirm" button of the popup. When you set the value of this data object to 'confirm' the system calls the processing logicnet to save the selected cause and to close the popup. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1b4df0b27a7cd81d6c26a9c685a1974088766b49%2F52b0bab6-fbe6-4226-b3c5-ced4a673168f.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/design-considerations-and-frameworks/frameworks/support-center-framework/customize-your-cause-selection.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.