> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/changelog/2024/november-2024.md). # November 2024 ### New features and improvements * We have introduced a [new templating language "ICL"](broken://spaces/-M76ygPnS4HUcFSX8ulm/pages/l0DnG2KVyQN3jcBKbyXf) for alert source templating. While improving the syntax, we now also support conditional blocks and loops. * A new internal alert action is available "Re-route" you may use this in combination with the unresolved or escalation ended alert events to automate a reroute action, assigning the alert to a different escalation policy. * **Audit logs** have moved into closed BETA, the long awaited enterprise feature. Let us know if you would like to try it out before it moves into GA. * Call flows now support a new node: **Block numbers**, it can be used to block unwanted incoming callers ### Integration updates * We have overhauled the Raygun inbound integration, it now supports multi-alert scenarios as well * There is a new deployment integration: [Gitlab](/integrations/deployment-integrations/gitlab.md) --- # 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.ilert.com/changelog/2024/november-2024.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.