> 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-tasks.md).
# Workflow Framework: Tasks
The LogicNets system allows you to add workflow functionality to applications you create using the Application Starter Portal Framework. This functionality supports the following:
* Task creation
* Role-based task actions
* Task lists
* Sequential and/or parallel workflows
* Task locking
* Persistent workflow data objects that can be passed between tasks
Workflows are modelled as logicnets like the one in the diagram below, but these logicnets are slightly different than non-workflow logicnets in that they contain task nodes.
Each task node represents a distinct step or unit of execution within the workflow, and the workflow steps from one task to the next based on the outcome of that task. Each task node has the following configuration options:
| Field Name | Description/Use | Type/Options | Optional/Mandatory | | |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | --------- |
| Task label | This is the label of the task as shown in the logicnet. | Text | Optional | | |
| Task type | This is the type of task.
- Choose user if the task requires user interaction.
- Choose system if the system executes the task in the background using a process called the system task runner.
| User \| System | Mandatory | | |
| Subject | This is the title of the task if it displays to users. | Text | Optional | | |
| Display | When this parameter is set to Yes the system assumes the task has a user interface and will render a top bar with navigation and action buttons. The system will also include a message area where validation errors display if necessary.
If this parameter is set to No the system assumes the task is a processing task or has a custom user interface that implements the navigation bar and errors if necessary.
| Yes \| No | Mandatory | | |
| Outputs | This is the outputs for the task. Each output has the following parameters:
- Value: This is the value of the output.
- Caption: This is the caption of the output value (only relevant for tasks with a UI).
- Applies to: This is the user role that is associated with the button. It is only relevant for tasks with a UI, and--when filled—the button is only visible to users with the specified role.
- Next status: This is the caption displayed on the button.
- Save: yes | no. This sets whether the system should save the task.
- Validation: yes | no. This determines if the system will step the task forward if there are validation errors. This is only relevant for tasks with a UI.
- Condition: This is the condition (f there is one) for enabling the output button on the navigation bar. This is only relevant for tasks with a UI.
| Collection | Mandatory |
| Actions | This parameter is only applies when Display is set to "yes". These are the buttons the system will display on the top bar for triggering another logicnet.
Each action has the following parameters:
- Caption: This is the caption of the action button.
- Applies to: This is the user role linked to the button. If this parameter is provided the button is only visible to users with the specified role.
- Call logicnet: This is the name of the logicnet to call when the button is clicked.
- Display: When set to "yes" the system will open the logicnet in a popup window.
- Parameters: These are the input parameters the system should send to the called logicnet. The system supports string interpolation, however, the interpolation happens at server side when the button is being rendered and not at the time the user clicks the button.
| Collection | Optional | | |
| Task net | This is the logicnet the system will call when the task is executed. | Logicnet | Mandatory | | |
| Load net | This is the logicnet the system will call to load task data. If this is not specified the system will load task data from default task storage. | Logicnet | Optional | | |
| Save net | This is the logicnet the system will call to save task data. If this is not specified the system will use the default saver. | Logicnet | Optional | | |
| Pre-process net | This the logicnet the system will call before the start of the task; for example, to pre-process data. | Logicnet | Optional | | |
| Post-process net | This the logicnet the system will call after the task logicnet; for example, to perform post-processing actions. | Logicnet | Optional | | |
| Parameters | These are the input parameters for the task. The system supports string interpolation. | Text | Optional | | |
| Planned start | This is the date after which the system must start the task. It is only applicable for system tasks. | Date | Mandatory | | |
| Tags | This is the meta-data associated with the task. Each tag has the following parameters:
- Type: This is the key of a tag. One predefined key is "role" but you can enter any key.
- Value: If the key is set to "role" the value specifies the role(s) to which the task applies. The task-locking mechanism will only allow a user to open task if the user has one of the specified roles. If no role is specified any user can open the task.
- Value-type: This is the type of the value: value | collection.
| Collection | Optional | |
---
# 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-tasks.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.