> 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/content-authoring-software-parts/logicnets-designer-ln-d.md). # LogicNets Designer (LN-D) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-28bf89b180d80dcd9e4a1aad95f728a33ef7128f%2Fd88d5d41-1fac-4b57-8992-961963d8ab78.png?alt=media) ### License Basis: Per Designer User. Notes: 1. REQUIRED COMPONENT FOR MINIMAL OPERATION … 2. …unless Customer acquires a turnkey Content Solution 3. Minimum of 1 designer user license per installation ### LN-D Description The LogicNets Designer is an interactive, browser-based environment that enables “subject matter expert” (SME) users to visually model their complex decision processes and thereby create applications that can interactively guide non-expert users through these processes as if they were the experts. Users working in the Designer create “projects” to visually diagram their process flows, “modeling” virtually any combination of decision steps which they can link together to form networks of decision pathways (“logicnets”). Each step can perform a wide range of automated functionality including: constructing HTML forms; collecting data interactively; accessing external environments via user-specified web services calls; linking to traditional digital content in local or external knowledge bases; preparing, managing, and transforming data; applying conditional logic; computing results; and producing and distributing formatted output. The LogicNets Designer includes a range of Editorial Tools to optimize the creation and management of logicnets content including: search, validation, debug, versioning, data model management, and more. These tools allow designer users to run their applications in different modes for simulating the user experience and rapidly finding and correcting errors in their modeling. The LogicNets Designer includes the “Publisher” which allows designer users to render one or a group of related projects as published packages to be accessed through a specific URL by authorized users. Published packages can be managed in the Designer and are by default hosted within the LogicNets instance for the Designer in which they were developed. The Publisher function also allows applications to be created as external packages that can be deployed on other servers or systems, such as Production systems. Designer users can also model a wide range of analytic processes to be used on data collected during run-time and which can be used to generate sophisticated reports. ### Services and Deployment Considerations No additional services are required for basic deployment of the LogicNets Designer. LogicNets Training Services (LN-TS) are available specifically to teach designer users how to create, deploy, and manage applications in the Designer. Note that some Designer functionality is specific to particular LogicNets runtime software parts such as use case Frameworks or Advanced Modules and these features will only be visible to designer users based on the additional components acquired. LogicNets Content Modeling Services (LN-CS) are offered to provide customers with qualified resources for modeling their decision-making content. This service is used to supplement or as an alternative to the organization’s use of internal resources. PG-CO1-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/logicnets-software-component-details/content-authoring-software-parts/logicnets-designer-ln-d.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.