> 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/january-10th-2025.md).

# January 10, 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>

* Made domain links in the app page clickable
* Added unsyncing for app clones
* Updated templates and scripts page table column width
* Google Enterprise License Manager integration

</details>

<details>

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

* Various fixes for crate replication in global Rewst regions
* Fixed OAuth token refresh for Google Enterprise License Manager
* Fixed UI crash when looking at forms permissions
* Added validation for domain length with org slug
* Added missing field to Halo Add or Update Quote action to update line items
* Fixed failing Duo List Phones action for non +1 country codes
* Fixed Pax8 auth token refresh

</details>

<details>

<summary><strong>Deployed behind feature flags awaiting QA review and feedback</strong></summary>

* Added Generic GraphQL Request Action to the Rewst Integration
* Github integration
* Granular forms permissions
* Cloning and Syncing of App Builder apps
* N-able N-sight integration
* SQL database integration refactor

</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/january-10th-2025.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.