Recently active topics

SummaryMoveworks currently applies global log‑redaction rules that often remove sensitive data from all payloads uniformly. While this protects customer information, it can make troubleshooting, debugging, and rule development extremely difficult when certain payloads must be visible temporarily or permanently.This request proposes a controlled mechanism to disable or override log redaction for specific payloads and specific key/value fields, using an extension to the existing redaction DSL. Problem StatementToday, log redaction is fairly extreme, and not easily refined at the project level (that I can tell)Redaction is applied globally Redaction cannot be disabled for specific data objects Redaction cannot selectively reveal individual fields Debugging issues in pipelines, transformations, audits and DSL logic becomes challenging without visibility into certain parts of the payloadAs a result, teams often struggle to analyze issues effectively without temporarily weakening overall log

Would be helpful to have an SDA on/off toggle on each plugin as we’ve noticed that it calls on some plugins that we don’t want it to run on. 

Hi Team,We’ve recently started using generation_text_action within Moveworks compound actions, incorporating LLMs with reasoning capabilities—specifically GPT-5.1.During this implementation, we noticed frequent time outs when handling high-reasoning requests and even occasionally with low-reasoning tasks, particularly when large contexts are provided to the LLM.As we embrace these new demands for reasoning models and more complex analyses, we would like to discuss the possibility of increasing the time out thresholds for compound actions. This change would not only enhance the capabilities of reasoning LLMs but would also support listeners that are highly dependent on compound actions. For instance, raising the time out limit would enable us to notify more users (e.g., beyond the current cap of 50) without compromising performance.We believe this adjustment will significantly benefit our workflows, particularly as we adopt more advanced models and use cases.Looking forward to your thou

I want to be able to manage what text is displayed during the “Thinking” step of my AI Assistant.Currently, the name of all the plugins being used are showing up on the screen. In some cases, these plugin names can be shown on the screen as 5 or 6 different lines, which can be noisy and look very robotic.We’d like to have the ability to update the language used while the user waits for a response, or at the very least limit the visibility to 1 or 2 lines on the screen for all plugins. 

One of the challenges as a Moveworks Admin and Dev is sharing with the users what prompts they have access to. There is no easy way to export all of them (even via the Support route) and keeping prompts up to date in a document or KB article requires manual effort.Microsoft has taken steps to resolve this issue for users with their Prompt Gallery. As of July, Microsoft will be building the Prompt gallery into the Copilot chat for even easier access.Changes to the Copilot Prompt Gallery app - Microsoft SupportFor best user experience, I would love to see Moveworks implement a solution like this in the AI Assistant as well. https://copilot.cloud.microsoft/en-US/prompts/all?ocid=CopilotLab_M365Chatofficeweb

Vision:Enable full native rendering and interaction with ServiceNow forms—including Client Scripts, UI Policies, Catalog Client Scripts, and UI Actions—directly within the Moveworks Web AI Assistant. This would allow users to complete forms without leaving the assistant, creating a seamless self-service experience.Why Now?With ServiceNow acquiring Moveworks, there's a unique opportunity to align platform capabilities. Moveworks may now have the technical control to support JavaScript execution safely within its Web AI Assistant, and ServiceNow can provide the necessary form logic and rendering components.💼 Business Value PropositionFrictionless User Experience: Users can complete complex forms directly in the Web AI Assistant, reducing drop-off and confusion. Increased Adoption: More users will engage with self-service workflows when forms are accessible and functional. Platform Synergy: Leverages the shared ownership between ServiceNow and Moveworks to deliver deeper, native integrat

Great to see that MCP servers are on the roadmap. Would love to see Agent2Agent Protocol (A2A) support being added too. It’s Open Source https://google.github.io/A2A/#/ Idea: Integrate the Agent2Agent (A2A) protocol to enable Moveworks' AI agents to seamlessly collaborate with other AI agents across various enterprise platforms.  Key Features:Inter-Agent Communication: Allow Moveworks' AI agents to communicate and collaborate with other agents from different vendors. Capability Discovery: Use the "Agent Card" feature to identify and leverage the best-suited agents for specific tasks. Task Management: Support efficient task management with real-time feedback and notifications. Modality Agnostic Support: Extend support for various modalities, including text, audio, and video. Enhanced User Experience: Provide a unified interface for users to interact with multiple agents seamlessly.Benefits:Increased productivity Cost efficiency Innovation through seamless agent collaboration 

To pull data from Employee Experience Insights table/view directly through an API to PowerBI for the purpose of creating a custom dashboard.

Currently in the EXI dashboard we can add custom filters to filter out the data based on different roles. A valuable enhancement to this would be the ability to provide role based access to different parts of the dashboard. For eg. A service owner should be able to filter out and view only the insights pertaining to their services.

in EXI --would be great to be able to use our own color schemes and have the ability to build and automate/export monthly reports based on a set of criteria and filters.  

Hello! I would like to put in a request for the following in EXI:In the “Employee Issues” dashboard, you can download CSV files of the tickets that are categorized in each of the 24 tiles on the employee issues heat map. The extremely beneficial information from these CSV files is the Topics column (that are determined via AI by reading the short description of the help desk ticket). The topics allow us to easily extract the main issues people are having/submitting help desk tickets for, and thus allow us to pinpoint the top issues.  The biggest downfall is that we need to manually download all 24 CSV files and combine into one file, which is time consuming. THE REQUEST: Add the ability to download a CSV file with all tickets that contain the Topic column (and the category type e.g., “Troubleshoot Information”; the same information that can currently be downloaded now for each of the tiles on the heat map). BUG: In the “Apps and Services Detail” dashboard, you can download one CSV

Our customer, WellStar, is requesting a capability to compare incidents (config items) year to year. I see that we are able to pull data from one specific quarter or year... but are there any plans to offer a timeframe comparison? Wellstar wants to be able to compare year to year or quarter to quarter. I imagine this would also benefit other customers as well.

Users are notorious for providing less-than-ideal descriptions of their Help Desk issues. It would be ideal for EXI to also leverage work and resolution notes (not just ticket description) when identifying ticket trends. (Similar to how Knowledge Studio leverages that data to write/suggest knowledge articles). Thanks!

We would like the ability to send employee communications using the Group Email section but we are limited to the Email Distro Lists that are in Active Directory. We have Dynamic Distribution Lists in Azure that has all of our users by department. We want to be able to target messages to specific email groups and are unable to do this because Moveworks currently does not support Dynamic Distribution Lists. 

As an admin, I would love if I were able to do additional things within Knowledge Studio. Such as:Enabling an admin to mark a suggestion as completed, not applicable, notes, etc. so we don’t have to try and remember which ones we have already worked. See history of items we have marked completed, etc. so that we can look at the history of what has been taken care of. More of an interactive “To-Do” view or “Task” oriented view would be helpful when filtering what suggestions we are able to actually turn into KBAs, and what suggestions are not applicable.Thank you for all you do!

When trying to create KB there is no visual hierarchy to understand the content in the KB. Can refer to the screenshot provided below. Same for Editor it does not contain rich text editor or simple editing where we can add bullet points to maintain hierarchy. The full title of KB is not visible, the title can be edited is difficult to understand as it has no signifier to it. No option to go back from this page, user need to go back to home directly, and it refresh the whole page which makes it difficult to follow up. No support for images to view or add images in the KB. No option to view number of articles to update when the article is opened for editing(Please refer 2nd screenshot)      

I saw in the Copilot feature overview that the unsubscribe etc are no longer possible in Copilot. For us this is a really important feature as it helps retain the users that have a lot of tickets open because they act as kind of a superuser for other people and open tickets for them. They get overwhelmed with notifications and like to mute some of them but would without that feature mute the bot entirely. Which would lower our active users significantly.Please bring that useful feature back, I don’t understand why it was not considered. 

Support Ambient Agent template installation from Marketplace.

ChallengeMoveworks ingests and surfaces archived Confluence spaces/pages because archived items remain reachable via deep links. This leads to stale content appearing in bot results and requires manual removal of spaces from ingestion whenever they are archived.Product IdeaEnable an option to automatically exclude archived Confluence spaces and pages from ingestion.Key points:Use Confluence’s existing status = "archived" metadata. Ignore spaces/pages marked as archived. Optional toggle in the connector: “Exclude archived content.” Prevents stale results and removes manual cleanup. Proposed EnhancementImplement logic in the Confluence connector to:Detect status = "archived" on spaces using the Confluence REST API (e.g., /api/v2/spaces/{id}). Exclude pages belonging to archived spaces from ingestion. Optionally detect archived pages (those with the /pages/archived URL pattern or other metadata) and exclude them individually. Provide a toggle in the Moveworks Integrations UI: “Exclude arc