> 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-accessing-workflow-data-from-within-a-workflow-or-task-logicnet.md). # Workflow Framework: Accessing Workflow Data from within a Workflow or Task Logicnet In addition to accessing workflow and task data from a storage table, you can also access this data from within the session context. In a workflow logicnet it is possible to access the following data: * *task\_details:* This is the data structure that contains all metadata of the currently active task within the workflow. It includes the following data options: | Field Name | Description/Use | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | type | This is the task type. | | selected\_option\_parameters | These are the design parameters belonging to the selected option. | | id | This the database record identifier for the task. | | workflow | This is the database record identifier for the workflow to which the task belongs. | | workflow\_root | This is the database record identifier for the root workflow to which the task belongs. | | locked | This flag indicates whether the task is locked or not. | | user\_id | This is the identifier for the user that last opened the task. | | status | This is the status of the task. | | selected\_option | This is the selected output of the task. | | roles | These are the user roles that are associated with the task. | | subject\_line | This is the title of the task. | | object\_id | This is the ID of the database record in the *generic\_task\_storage* table that stores the data for the workflow instance to which the task belongs. | | created | This is the date on which the task was created. | | last\_updated | This is the date on which the task was last updated. | * *WorkflowStarterParams.data:* At the start of the workflow logicnet this contains the input data the system passes into the workflow from the *Start Workflow* task node. * *dataobject\_data:* This is the data object that contains the actual task data. While the user or system executes a task the following context information is available: * *dataobject\_data:* This is the data object of the workflow and the system saves it when a task is closed. * *\_taskmetainfo:* The metadata is defined in the *task\_details* section above. Tasks and workflows run as local data. When a user or the system starts a workflow the workflow logicnet runs in a *WorkflowContext* and the *WorkflowStarterParams* contains the input data for that workflow. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3e5d727967a1f4412070dce1d303c8208f26c9a8%2F73a0464c-a7d8-49e0-a41a-0483d9c10a2b.png?alt=media) When a user or the system starts a task the task logicnet runs in a *task\_scope* context. When the task is closed and the workflow logicnet steps forward the workflow logicnet runs in the *TaskContext*. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-b848d601d0f775a96631e066a72430dd7cab70bf%2Fd55bf848-97c1-4797-af85-eb049044de28.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/workflow-framework/workflow-framework-accessing-workflow-data-from-within-a-workflow-or-task-logicnet.md?ask=&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.