> 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/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/september-23rd-2022-context-switching.md). # September 23, 2022 - Context Switching In this call, we're going to talk about our new Context Switching as well as a client demo on automating campaigns within CWM! Finally, we'll finish with a Live Q\&A about all the things you want to know! {% embed url="" %} ## Contents of the recording
Contents of the Call This call is for people who are: Interested in building their own workflows Wanting to stay on top of new developments Just want to learn more about Rewst and participate in the community We will talk about the platform, news, some training, and any Q\&A. As always, feel free to unmute and interrupt us, this is an interactive call! ​
How to get help from the ROC How to get help - Engage the ROC in Slack - Email support coming soon! - \[FUTURE] Live chat in the app - Would this be helpful to people? - Documentation - - Feature Requests -
Updates for the week Dev Team New Features * Invite User to Rewst (Demo) * Added per-task org context switching to allow users to run actions as managed organizations * Added “Get External Reference” action to the Rewst pack * Added ability to use tables in Markdown sections * Export: UI enhancements and error reporting * Added navigation links to tasks in Results Summary to allow users to open a particular task in a workflow * Added “Custom Field Conditions” filtering to CW Manage list actions * Added support for MFA and jinja templates to CW Control integration ​ Bug Fixes * Fixed issue where ImmyBot options for Computer ID wouldn’t show all results * Added a confirmation modal to results delete button * Optimized “Suggest Values” for integration org variable matching * Optimized storage of running workflow contexts * Removed unused components from frontend package * Updated Datto PSA option labels to use name instead of title ​ **In Progress** Dev Team In Review/Test * Settings page improvements * Support for signing up with Google Workspace accounts * Async Jinja when rendering tasks or within Jinja Context ​ Coming Soon! * Fix trigger criteria for ConnectWise Manage so we don’t run a workflow on every ticket updates ​ ROC * User Offboarding * Risky User Handling * Augment tickets with useful info such as IP-Info, user details, admin links * Options to close issue / escalate / disable account / reset passwords
Learning Topic * Demos * ORG Switching * Markdown in Pods * Invite User to Rewst * Variable Scoping across branches (isn’t a thing)
Show & Tell * Devin Scholl * Campaign Group Notifications
--- # 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/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/september-23rd-2022-context-switching.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.