> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/development-updates/2024-dev-updates/may-24th-2024.md).

# May 24, 2024 - Dev Update

Explore what new changes the Dev team has deployed in the last week!

This can be anything from new features, bug fixes, or QoL changes!

<details>

<summary><strong>New features and items</strong></summary>

* Stay tuned for more updates!

</details>

<details>

<summary><strong>Bug fixes and chores</strong></summary>

* Fixed labels for pie and doughnut charts in App Platform
* Use the correct width property for accordion components in App Platform
* Add support for orgs that require immutable id's to the Microsoft Cloud Bundle
* Updated the Datto Autotask setup instructions
* Fixed the jinja uuid4 generator to return uuid4 strings not uuid7
* Added handling for message sizes that exceed kafka limits and return an accurate error message for those failures
* Added a notification to the form builder if the user attempts to navigate away with unsaved changes
* Added handling for database integration errors
* Ensure the context send to render\_jinja are the correct data types
* Update Synnex integration name to TD SYNNEX Stellr
* Added a null check to fix a bug in App Platform data tables

</details>

<details>

<summary><strong>In review, testing and development</strong></summary>

* SAAS Alerts integration (In QA)
* ServiceNow integration (In development)
* Workflow version control (In Review)
* Add org mapping to Custom Integrations V2 (In Review)

</details>


---

# 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.rewst.help/updates/development-updates/2024-dev-updates/may-24th-2024.md?ask=<question>&goal=<user_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.