> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/rules/common-rule-features/input-and-output/simple-editor.md). # Simple Editor We recognize that not all users are familiar with JSON structure, so we offer a simple tool to easily create input and output objects. ## Working with the input & output model editor

{% hint style="danger" %} After making any changes to the input/output model, be sure to save them by clicking the **Save** button in the bottom-right corner. Please note that all changes apply only to the current version of the rule. {% endhint %} {% hint style="info" %} There are no limitations when creating input/output models. A model can have an unlimited number of root objects and child objects. {% endhint %} ### Adding a Root object To create a root object, click ![](https://437457296-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MN4F4-qybg8XDATvios%2F-MQStuejyHo4-2lJXf6Y%2F-MQT2spzTHmRZpO8lZLe%2Fscreenshoteasy%20\(7\).png?alt=media\&token=b775e2dc-72f5-4a1b-9c4f-8221622bfc34) button. ### Adding a Child object To create a child object, click **+** sign on the parent object.

### Moving an Object (Dragging) To move an object to another parent or make it a child, drag the object and drop it on the desired parent. To make a child object a parent, drag it and drop it at the same level as the current parent.

### Showing Child Objects To view child objects, click the arrow next to the parent object.

### Deleting an Object To delete an object, click the **Delete**

button on the object. ### **Viewing Object Structures** To display the entire structure and all objects, click the ![Expand All](https://437457296-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MN4F4-qybg8XDATvios%2F-MQStuejyHo4-2lJXf6Y%2F-MQT3bAIBAWHNsHgyKw-%2Fscreenshoteasy%20\(8\).png?alt=media\&token=0c3d8b36-7035-42f7-80a5-f9eb8ccdbe91) button. To view only parent objects, click the ![Collapse](https://437457296-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MN4F4-qybg8XDATvios%2F-MQStuejyHo4-2lJXf6Y%2F-MQT3Y4J-AIqgvpah9pQ%2Fscreenshoteasy%20\(9\).png?alt=media\&token=7642d271-003b-4766-b75a-5d6609373386) button. ### Renaming an Object To rename an object, click its name. An input box will appear. After making your changes, click outside the box or press **Enter** key to close it. {% hint style="warning" %} Only letters, natural numbers, underscores and hyphens are allowed. {% endhint %} --- # 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://docs.decisionrules.io/doc/rules/common-rule-features/input-and-output/simple-editor.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.