> 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/marketplace-updates/2024-marketplace-updates/november-22nd-2024.md).

# November 22nd, 2024 - Marketplace Update

Explore the new changes to the Marketplace in the last week!

This can be anything from new crates, enhancements, or bug fixes!

<details>

<summary><strong>New crates and enhancements</strong></summary>

* Rewst: User Onboarding
  * Added contact\_id to workflow input so users using the workflow as a wrapper can specify the field used in initial ticket creation.
  * Deployed refactored version of Configure Out of Office Mailbox crate.
  * Deployed refactored version of Amend Mailbox Permissions crate.

</details>

<details>

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

* Get and Set Org Variables
  * Changed the Connectwise Automate and Kaseya VSA transition custom conditions to switch based on their correct identifiers. Were previously set to datto\_rmm.

</details>

<details>

<summary><strong>Coming soon!</strong></summary>

* App Builder Apps
  * Operational Analytics Portal - aggregates data from various tools and outputs actionable insights for MSPs to further streamline operations.
  * Forms Portal - allows employees and clients to easily access the necessary Rewst forms based on granular permissions.
  * All-In-One Client Portal - The portal transforms service delivery by empowering clients to instantly self-serve common IT requests —not just submit tickets.
* Top 10 crates - Improving success rates and implementing Rewst Best Practice
  * Alert when Mailbox Quota Full
  * Detailed MFA Reporting
  * Refactor of Change a Users Password form. (just needs QA)
  * Refactor of Identify DUO users in Bypass Mode. (just needs QA)

</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/marketplace-updates/2024-marketplace-updates/november-22nd-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.