> 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-templateexample-project.md).

# Workflow Framework Template/Example Project

This is a simple 3-step workflow to demonstrate the LogicNets Starter Application workflow library, and you can use it as the template for your own workflow.

### Customization Points

To begin customizing this project to your specific needs, look at the following:

* Change the name of the workflow: The name of the workflow is set in the data object called ‘workflow\_name’ in the *init* logicnet in the *onstart* folder.
* Add/edit tasks in the workflow: In the *my\_workflow* logicnet, edit the existing tasks or drag new tasks into the flow from the toolbar. *ui task* is the most common type of task, but you can also choose *bgnd task* or *wait task.* See the Subworkflow example project for more information on this.
* Customize the task header: A simple task header is included to show the instance Id of the workflow and the task, and the task options are rendered as buttons. When you want to re-style this header you can update the *task\_header\_generator* logicnet.

### Library Files

The logicnets in the "lib" folder are generic logicnets that are required for the system to trigger the workflows. Generally, you will not need to make any changes to these logicnets for your specific workflow project to run.

### Workflow Settings

Some of the system configurations for workflow include data storage location, task authorization and locking, and time stamps.

You can change these in the *Project Settings/Framework* tab as shown below. See [this](/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-customizations-data-location-check-for-task-authorizations-task-locking.md) article for more information.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f6e7c116ae73a635cb0202efe10d90ecd37ada42%2F15110344-a37c-43a2-9831-98f15757d0d3.png?alt=media)

## Attachments

* [Workflow Application Template.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/80gvms-Workflow-Application-Template.zip)


---

# 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-templateexample-project.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.