> 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/other-help-articles/definitions.md). # Definitions | Term | Definition | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Data Object** | An item that names a particular piece of data and/or information. For example, if you want to ask a user to enter his or her name, firstname is a data object and lastname is a data object. | | **Editor** | The tools in LogicNets through which you edit or update steps, logicnets, projects, and resources. Each step type has its own editor, which gives you access to the actions your application can take using that step. | | **Framework** | A framework is the backbone of an application. It is the group of logicnets, data tables, and resources that LogicNets created to run your content. A framework does all the work of displaying your content and collecting and saving data and allows you to focus on modeling your expertise in logicnets. Each framework has been created to perform specialized functions. | | **Group** | If you have a lot of data objects, you may want to keep certain items together by "grouping" them. For example, if you are asking someone for their name and address as well as the name and address of their manager you might have a group called *customer\_information* with *firstname*, *lastname*, and *address* data objects and you might also have a group called *manager\_information* with *firstname*, *lastname*, and *address* data objects. To set the name of a group, you enter the group name first when you name your data object, then enter a period, then enter the name of your data object; for example, *customer\_information.firstname*. | | **LogicNets** | The online application/software used to build, publish, and maintain applications. | | **Logicnet** | A logicnet is a series of steps that you combine to create a logical progression of actions for performing a particular task or procedure. Each step in a logicnet represents a distinct set of instructions the logicnet will carry out as part of the overall application or process. An application can consist of one logicnet or it can be made of multiple logicnets that you link together. | | **Node** | The individual building block you use to create a logicnet. We also call this a step. | | **Form Node** | This is a user-facing step in your application that contains text, images, and other items the user sees. Used to present information to or retrieve input from a user. | | **Process Node** | This is a system-facing step in your application that contains actions the system performs. Used for processes and operations not visible to the user. | | **Project** | A collection of one or more logicnets and all the associated images, documents, and data that you combine to create a custom application or program. | | **Publish** | The process of translating your project into a working application or program for others to use. | | **Resource** | Images, databases, documentation, and other information that you can link to or access from your logicnets. | | **User** | The individual or group authorized to access and use your working application. | --- # 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/other-help-articles/definitions.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.