> 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/2025-dev-updates/july-18-2025-dev-update.md).

# July 18, 2025 - 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>

* **Crates**
  * Improved reliability of automatic crate sync process by removing manual sync of forms
* **Integrations**
  * Added support for custom HTML branding in core confirmation messages.
  * NinjaOne integration now includes new actions for ticketing and documentation.

</details>

<details>

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

* **App Builder**
  * Fixed issue by preventing unnecessary conversion of HTML code into React elements.
  * Ensured reserved keyword "microsoft" is correctly validated and disallowed in Custom Domains.
* **Dashboard**
  * Fixed inconsistency between chart and table task counts.
* **Engine**
  * Improved workflow success and failure internal visibility for improved planning
  * Enhanced storage efficiency and performance by implementing Msgpack+Zlib compression for workflow execution contexts.
  * Improved Msgpack encoding handling to align with existing JSON handling standards.
  * Resolved handling of null characters within JSONB data.
  * Fixed bigint-to-number conversion after Msgpack unpacking to prevent GraphQL issues.
* **Integrations**
  * Fixed Microsoft Graph integration issue preventing subscription setups for groups and user changes.
* **Workflows**
  * Removed unnecessary search text filter from sub-workflow views.
  * Eliminated legacy `process_new_workflow` feature flag.
* **Crates**
  * Improved Crate Marketplace by hiding the "uncategorized" category when empty.
  * Updated crate replication logic to bypass feature flagging tool for API users.

</details>

<details>

<summary><strong>Coming Soon</strong></summary>

* DropSuite integration
* BVoIP integration
* Leader Integration

</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/2025-dev-updates/july-18-2025-dev-update.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.