> 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/august-29-2025-dev-update.md).

# August 29, 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**
  * Added GPT-5 models to chat completions configuration
  * Updated Hudu integration icon
* Updated Sign in with Entra ID to Sign in with Microsoft on the login page

</details>

<details>

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

* **Integrations**
  * Fixed 500 error in `connect_wise_psa_update_service_ticket` action when using custom property
  * Resolved ConnectWise PSA country list fetch issue causing 500 errors
  * Fixed ConnectWise PSA service survey data retrieval issue
  * Improved Acronis workflow handling:
    * Allowed body in Acronis forms header to be sent as an object when form data is set as a header
    * Enabled custom headers to be processed by the Acronis generic API action
  * Correctly handle non-iterable values in parameter input arrays
  * Removed obsolete dashboard code related to integrations needing attention
* **Org Variables**
  * Enforced required organization variable fields to prevent error on save
* **App Builder**
  * Fixed an issue where creating new page-level permissions didn’t also grant the related app-level access, causing inconsistent behavior between page and app permissions.
* **DevOps**
  * Improved cherry-pick handling for patch-release workflow

</details>

<details>

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

* DropSuite integration
* BVoIP integration
* Leader Integration
* Hourly dashboard updates

</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/august-29-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.
