> 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/logicnets-software-component-details/general-runtime-components/frameworks.md). # Frameworks ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-9775653729351e4c51d819926574f151b0a79973%2F51565f7e-818a-4447-adac-0ae176ea4279.png?alt=media) ### Frameworks Description “Frameworks” are pre-configured applications built in LogicNets that provide the infrastructure to match modeled logic to the use case requirements. “Use Case” Frameworks implement a specific interactive user experience around the organization’s modeled content to match the requirements of a particular use case. Function Frameworks provide special processing capabilities, such as presenting a web service API to external systems, that can be layered on other LogicNets applications to enhance the overall available functionality. LogicNets Frameworks are highly configurable and can even be combined with customer-built customization layers to meet the specific needs of the organization. The use of frameworks allows the organization’s subject matter experts (SMEs) to focus on modeling their expert process knowledge by separating that modeling from the components in which application behavior is controlled. LogicNets has identified a range of common application use cases and created preconfigured frameworks that automatically deliver the required application behavior for that use case separate to SME-modeled content. For instance, Use Case Frameworks can divide the screen into multiple, contextually linked functional areas, each of which can run separate SME-modeled content, automatically coordinating the relationship between those areas…for instance, collecting user input in one screen area and dynamically generating computed results from processing of that input in another area. Note that Customers can re-configure LogicNets-provided frameworks or they can even create their own framework applications to meet their own unique requirements. ### Services and Deployment Considerations Frameworks can be reconfigured and/or customized with the support of LogicNets Pro Services either through: 1. Design and Deployment services in which LogicNets implements functionality 2. Training Services to enable customer staff to configure standard features or create their own “custom” frameworks ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a8c750b2f623e94950ad170ae84d5d44440c69d1%2F2cbce9f3-2841-42cc-98ca-c62bd1e76f18.png?alt=media) [LogicNets Assessment Framework (LN-ASF)](/release-9/platform-documentation/sales-materials/logicnets-assessment-framework-ln-asf.md) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a8c750b2f623e94950ad170ae84d5d44440c69d1%2F2cbce9f3-2841-42cc-98ca-c62bd1e76f18.png?alt=media) [LogicNets Support Center Framework (LN-SCF)](/release-9/platform-documentation/sales-materials/logicnets-support-center-framework-ln-scf.md) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a8c750b2f623e94950ad170ae84d5d44440c69d1%2F2cbce9f3-2841-42cc-98ca-c62bd1e76f18.png?alt=media) [LogicNets Visual Guidelines Navigator Framework (LN-VGN)](/release-9/platform-documentation/sales-materials/logicnets-visual-guidelines-navigator-framework-ln-vgn.md) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a8c750b2f623e94950ad170ae84d5d44440c69d1%2F2cbce9f3-2841-42cc-98ca-c62bd1e76f18.png?alt=media) [LogicNets Starter App Framework (LN-SAF)](/release-9/platform-documentation/sales-materials/logicnets-starter-app-framework-ln-saf.md) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a8c750b2f623e94950ad170ae84d5d44440c69d1%2F2cbce9f3-2841-42cc-98ca-c62bd1e76f18.png?alt=media) [LogicNets Knowledge Center (Run-Time User) (LN-KCU)](/release-9/platform-documentation/sales-materials/logicnets-knowledge-center-run-time-user-ln-kcu.md) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a8c750b2f623e94950ad170ae84d5d44440c69d1%2F2cbce9f3-2841-42cc-98ca-c62bd1e76f18.png?alt=media) [LogicNets Web Services Framework (LN-WSF)](/release-9/platform-documentation/sales-materials/logicnets-web-services-framework-ln-wsf.md) PG-FR0-231127 --- # 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/logicnets-software-component-details/general-runtime-components/frameworks.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.