> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/portal/rule-engine/new-rule-engine/rule-engine-table-overview.md). # Rule Engine Table Overview You can add columns to your Rule Engine Overview to have a better management in your notification and automation centre. Datacake now allows you to add columns and search **by name** inside of the Rule Engine. You can also sort ascending or descending by columns, just like in the Device List overview. The column options as for March 2025 are: * **Enabled:** Green tick symbol (✅) if rule is enabled, gray cross symbol (╳) if it is disabled. * **Name:** Assign a name to your rule in the Edit Rule mode. * **Description:** Assign a sinful description to your rule in the Edit Rule mode. * **Product:** Now you will be able to see the products selected as triggers inside of your rules. * **Actions:** We have icons for email, SMS, webhook, single device downlink and multi-device downlink actions, which now you can see without having to enter the Edit Rule mode. Check out a short video about the feature here: {% embed url="" %} --- # 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.datacake.de/portal/rule-engine/new-rule-engine/rule-engine-table-overview.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.