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 article for more information.