> 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-4-2025-dev-update.md).

# July 4, 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>

* **Integrations**
  * Crushbank integration - Documentation can be found [here](/documentation/integrations/integration-guides/crushbank-integration.md)
  * Added Slide integration actions for device pairing
  * Enhanced Microsoft CSP integration with customer link/unlink actions
  * Improved YAML parsing with new transform actions
  * Included response headers in CSP Generic API requests
  * Added disaster recovery and incidents actions to Acronis integration
  * Added Superops new ticket polling sensor
* **App Builder**
  * Added the ability to edit components within a dialog
  * Enhanced Size settings for the Text V2 component

</details>

<details>

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

* **Crate Marketplace**
  * Added missing integrations for filtering functionality
* **Forms**
  * Improved performance for form loading by resolving duplicate queries that caused Apollo cache misses
* **Integrations**
  * Corrected auth\_base\_url subdomain for FlexPoint
  * Added headers option to generic Custom Integration requests
  * Increased test coverage for Asana integration
* **Workflow Builder**
  * Fixed trigger version history extending off the page
  * Removed stale feature flags and stale code

</details>

<details>

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

* DropSuite 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-4-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.