> 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-the-storage-of-meta-data-related-to-selected-causes-and-observations.md).

# Customize the Storage of Meta Data Related to Selected Causes and Observations

The Support Center Framework will store the selected cause, observations, and associated meta data when the user clicks ***SUBMIT***. At this point, the system saves the observations (Questions & Answers) and causes to the tables--either default or custom, depending on configuration choices. The system immediately updates the probability bars for the next troubleshooting session.

If you want to customize the information stored in those tables, you can model an alternative *store causes* logicnet and call it via the framework setting (see image above).

See the [SCF Data Tables](/release-9/design-considerations-and-frameworks/frameworks/support-center-framework/support-center-framework-data-tables.md) article for more information about the default data structures saved on submit, or contact your LogicNets Account Manager for a copy of the default *store causes net* for you to edit and customize.

**Special Case**

One special implementation of this functionality is to DELAY the saving of observations and causes by creating an empty store-causes logicnet (e.g., a single empty process node). This prevents data from being stored to the observations and causes table at the submission point. This is very useful if there is additional downstream processing by the user; for example, to confirm at a later point that the selected cause and corrective action had the desired effect.

The modified architecture diagram below shows how a Starter Application can interact with a Support Center Framework application to delay confirmation of cause beyond the initial submission action.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2312c1ff81c830f841285605b5b620ca1d092058%2F308c7d18-bca9-4c39-a84c-f4d32f0275c2.jpg?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-the-storage-of-meta-data-related-to-selected-causes-and-observations.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.