> 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/workflow-framework/workflow-framework-database-tables.md).

# Workflow Framework: Database Tables

As part of the Workflow framework, the system saves all workflow data in a database and follows this information model for workflow data:

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-752db3bff0a08f3009fc83d4d1b17c30ac7dfbb9%2F63bea79a-e668-4250-bdc8-9fd42d337e5a.png?alt=media)

The system stores workflows and tasks in specific tables, and you can query these tables and display them on screen to display tasks. The workflow and task tables include the following:

* *generic\_task:* The system stores all instances of tasks from all workflows in the *generic\_task* table and provides each instance of a task a unique identifier. The system stores this id in the *workflow\_instance* column of the *generic\_task* table. With this ID you can retrieve all tasks associated with a particular workflow.
* *generic\_task\_storage:* The system stores persistent workflow task data as a single BLOB in the *generic\_task\_storage* table. All tasks from the same workflow share the same data container, so you can pass this data between tasks in the same workflow.
* *generic\_task\_tags:* The system stores tags associated with each task in the *generic\_task\_tags* table. Each task tag is linked to a task by its id.
* *generic\_workflow:* The system stores all instances workflows in the *generic\_workflow* table stores all the instances of workflows. Each instance of a workflow is uniquely identified by its id, this id will be used throughout the other tables for linking to the workflow.
* *generic\_checker\_workflow:* The system stores the link between parent and child workflows in the *generic\_checker\_workflow* table. This allows the system to execute parallel workflows and step a parent workflow forward whenever a task in a child workflow is completed.


---

# 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/workflow-framework/workflow-framework-database-tables.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.