> 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-customizations-data-location-check-for-task-authorizations-task-locking.md).

# Workflow Framework Customizations: Data Location, Check for Task Authorizations, Task Locking

The Workflow framework has to capability of locking tasks to ensure that a task is only accessed by one user at a time.

## Data Location

By default, the framework saves workflow data to a local SQLite *workflowdata.db* database. You can, however, configure the system to save workflow data to a different storage location by performing the following steps:

1. In the Project pane of the Designer select your project.
2. Click the *Modify* button in the viewer pane.
3. Click the *Framework* tab and scroll down to the *Worfklow: data location* setting.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4deb2c29d50332a617693b937604bc8a50f3900f%2Fb1201090-962f-4891-bc4c-c3b3dc623c92.png?alt=media)
4. If you want to store data in a different SQLite database enter the name of that database. If you want to store the data in ODBC-linked database enter the the name of an ODBC connection string; for example, *"odbc:DSN=MY\_DATA"*. In this example MY\_DATA is the ODBC connection to an external database.
5. To change the names of the workflow tables you can use the "settings.cfg" file.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4d5110c596a9afe6f524c147790528014706e6d7%2F4e1b0916-6dad-4e23-9106-de1fd18b39e3.png?alt=media)

Note: The tables in external databases must match the following table definitions.

## Task Locking

To switch on or off task locking perform the following actions:

1. In the Project pane of the Designer select your project.
2. Click the *Modify* button in the viewer pane.
3. Click the *Framework* tab and scroll down to the appropriate setting.
4. Click the checkbox next to this setting.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-559a76ba088af9bc78f81bf5b64d5caa3785b88b%2F927b73c5-30b7-4b34-88b1-35f0acce4707.png?alt=media)

## Task Authorizations

By adding role tags to tasks you can specify that the framework checks whether a user has the role required to open a task. First, you specify roles in your model and then in the configuration settings you specify if the system checks for user roles. To configure a task authorization check perform the following actions:

1. In the Project pane of the Designer select your project.
2. Click the *Modify* button in the viewer pane.
3. Click the *Framework* tab and scroll down to the *Worfklow: enable check for task authorizations* setting.
4. Click the checkbox next to this setting.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a0b0eb88052657856af7b6105404890a1bacf96e%2F13cdbb84-9d94-46f2-b3ca-6283e328025f.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-customizations-data-location-check-for-task-authorizations-task-locking.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.