> 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/2022-dev-updates/november-4th-2022.md).
# November 4, 2022 - 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!
New features and items
* Workflow completion listeners (workflows triggered on completion of another workflow)
* Add a maximize button for the task editor code view
* SSL support for AWS and Azure database connections in the database integration
* Added a Rewst action to list installed integrations for an organization
* Added Kaseya BMS actions
Bug fixes and chores
* Fix: Add newer features to export/import so they are included in export data
* Improved formatting for errors coming from our api that might be displayed in result details
* Fix a bug where CSP is preventing users from sending impersonated emails
* Refactored permission system to use database notifications to sync users and orgs
* Improved performance for frontend and the api resulting in improvements in page load time
* Fixed a bug with SQL Server database integration preventing the list\_all\_tables action from succeeding
* Enhanced logging for Kaseya VSA to capture additional information for an un-resolved bug
* Fixed immybot integrations page returning a 500 error
* Added support for an edge agent for the permission system
* Added a /healthz endpoint to the engine to improve health checking
* Prevent an empty string from being entered when selecting “In” or “Not In” for trigger criteria before entering a value
* Fix ExchangeOnline cmdlet proxy errors when converting an email to a shared mailbox
In review and testing
* SonicWall NSM integration
* Add role attribute to the rewst Create User Invite action
* JumpCloud integration
* Fix CW Control not running powershell scripts correctly
* Fix dynamic dropdowns loading and lifecycle
* Allow select form dropdowns to have the option of user supplied input
In Development
* Automatically retry http requests on connection errors
* Add periodic token refresh so in the case of an integration not being used for a long time, the refresh token doesn’t expire
* Investigate a bug report regarding Integration Overrides being removed when a user re-authenticates MS Graph
* Add a delete button to the org table in settings to allow users to delete an org
* Allow filtering the workflow list by tags
* Investigate a bug where Triggers aren’t cloning in some cases
* Investigate a bug where cloning a Workflow is blocked with a message indicated it’s linked, but the UI is not showing it as linked
If you'd like to see these in action, review the latest [Open Mic recording here](/updates/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/november-4th-2022-your-workflows-are-listening.md)
---
# 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/2022-dev-updates/november-4th-2022.md?ask=&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.