> 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/platform-documentation/sales-materials/logicnets-workflow-module-ln-wff.md). # LogicNets Workflow Module (LN-WFF) ### License: per user of Workflow Module-driven applications Notes: 1. Supports use of both named and concurrent user licenses 2. Can be used in conjunction with the Base System and all LogicNets Use Case Frameworks to invoke and manage applications as part of a workflow 3. When used to automate web services-based non-interactive applications, must be licensed on a web services transactions basis. ### LN-WFF Description The Workflow Module is a set of LogicNets parts and plug-in libraries that enable LogicNets models to appropriately handle complex workflow tasks. With the Workflow Module, as LogicNets applications execute their modeled workflow, they create tasks and invoke corresponding automated task management processes. Tasks are assigned to machine and human users based on their respective roles. The system is then capable of monitoring and evaluating task progress and automatically transitioning through workflow task sequences and assigned users. The WFF can use web services to interact with external systems, invoke LogicNets processes in the base system, and invoke LogicNets Framework applications for structuring delivery of modeled processes. The Workflow Module is usually deployed with the Starter App Framework as the means of giving users visibility into the tasks that have been assigned to them, task status and the ability to open a task, complete it, and progress through the managed workflow. The tasks managed by the WFF are typically implemented in LogicNets as projects built on either the base system or one of the frameworks, such as the ASF. ### Services and Deployment Considerations The Workflow Framework requires LogicNets Design and Deployment Services (LN-DS, LN-TS) since this module is in BETA. Services include: * Configuration of the Designer to support customer workflow concepts * Customer-specific user and task management configuration * Integration with external applications, including task, scheduling, and user management systems * Workflow Designer training These services usually require development and acceptance by customer of a formal SoW. PG-AD1-260217 --- # 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/platform-documentation/sales-materials/logicnets-workflow-module-ln-wff.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.