Skip to main content

    Filter by idea status

    Filter by product

    1344 Ideas

    Selective Log Redaction Overrides for Specific Payloads and Fields4. Future Consideration

    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 safety.Proposed Solution: Redaction Override ruleExtend the existing Moveworks redaction rule to support a new structure that allows per‑payload and per‑field exceptions.{ "show": { "info": [ "data.anotherPayload.Name.First" ], "debug": [ "data.myPayload" ] }, "redact": [ "data.sensitive", "data.userPayload.user_choice" ]}How it would work show list Any paths listed under "show" are preserved in full. Full objects (e.g., data.myPayload) can be whitelisted. Individual fields (e.g., .Name.First) can also be whitelisted. show info/debug  Info or Debug settings mean that item will log in production mode or debug mode. For logging info mode there would be a simple log entry that shows just that payload, this might be similar to accessed_variables in the logs. redact list Specific objects or fields can still be forcibly redacted even if part of a visible payload. Final redaction behavior Redaction system evaluates "show" rules first (explicit allowlist). "redact" takes precedence for any subfields explicitly listed. Any data not mentioned falls back to existing platform defaults. at the kick off a plugin - the redaction rule would show in the logs on the info entry. BenefitsFor DevelopersCan fully inspect problematic payloads during debugging Reduces friction and time to resolution No need to disable global redaction settingsFor Security & ComplianceOverrides are explicit, documented, and controlled Redaction remains applied everywhere except where explicitly allowed Still enables field-level protection for sensitive subfield dataFor Platform ConsistencyBuilds on the existing redaction DSL Maintains an opt‑in model rather than broad “disable redaction” switches Minimizes implementation complexity while maximizing flexibility

    taylorkf15Known Participant

    EXI: Adding Topics from Employee Issues Map to Apps & Services Detail4. Future Consideration

    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 file for all tickets, but there the information in the “Topic” column and TTR when you download the file is wrong. If this is fixed, this may solve the issue, but it would be ideal to be able to include the ability to download a file of all tickets within the given timeframe on both the “Employee Issues” and and “Apps and Services” Detail dashboards that includes a column with the topics.  

    jyuEmployee

    Ambient Agent Installation Support4. Future Consideration

    Ambient Agent Installation Support in Mktplace -- now live in Agent Studio!A large friction point that we've heard from builders has been: "I found an ambient agent on the Marketplace, but there's no install button -- I have to rebuild everything from scratch." Manually recreating compound actions, trigger configs, webhook listeners, and JSON mappings by hand was a non-starter for most teams.That’s over: you can now install ambient agents directly from the Marketplace into your environment with a single flow! Webhook plugins, scheduled trigger plugins -- they all install cleanly and come with all their compound actions and JSON mappings imported automatically. The same process also powers dev-to-prod promotion, so sandbox-to-production workflows are first-class.What's included:One-click Marketplace installation -- ambient agents now have an Install button. No more manual recreation. Automatic asset import -- compound actions, trigger configurations, and JSON mappings come along for the ride. Smart asset resolution -- if a component name conflicts with something already in your environment, the installer allows you to rename your existing asset seamlessly. Dev-to-prod promotion -- the exact same process powers promoting ambient agents from sandbox to production.How it works:Find an ambient agent on the Marketplace Click Install -- you'll see the installation flow For webhook plugins: choose an existing listener from the dropdown, or configure a new one in the installer If any asset names conflict with your environment, choose to use the existing asset or set up a new one Review your configuration and publish when ready Try it out and let us know what you think! Feedback and requests welcome.

    afleury
    afleuryInspiring

    Confluence Connector - Add support to hide Archived spaces.1. New

    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 archived spaces” “Exclude archived pages” Ensure Moveworks search results return only current knowledge matching what users see in Confluence. Note: I’ve already raised a support ticket and the team have confirmed this is currently not possible. Only workaround is to adjust Space Keys URL to add “Archive” to them then apply a DSL filter which is not ideal. e.g. NOT (("archive" IN article.article_url.$LOWERCASE()))

    Thomas.CoffeyKnown Participant

    Analytics Enhancement Request1. New

    Within my organization, my team consistently receives requests for Edison metrics - Particularly, organizations are interested to know the % of their team members are leveraging AI to assist them with daily tasks. The filtering options that are currently available on the Analytics application do not easily allow for a user to filter down to a select organization - For example, our Core HR team wanted to understand their utilization of the AI Assistant and the organization of 1K individuals were made up of over 200 departments that had to manually be added into the analytics app. My recommendations for the analytics application are:Allow Moveworks customers to add additional fields, from ServiceNow in my case, to filter on within the Analytics Application If fields such as cost center or supervisory org could be included this would elevate the pain point of only being able to use the smaller department field  Allow Moveworks customers to upload a csv of email addresses to filter on the user interactions the team is interested in  I envision this capability would work similar to the employees comms capability to upload a csv to determine the target audience - this enhancement would allow users to upload a csv to determine the scope for looking into interaction metrics Allow Moveworks customers to easily view when the bot proactively sends Agent Studio messages  Currently we can only view the user interactions, we had to create a ServiceNow table that tracks when our bot sends messages, however it would be convenient to be able to track the messages sent, in the same place as the interactions are I understand the Data API could potentially elevate these pain points and allow our organization to gain more value from the metrics being captured in the analytics application. However, I believe adding these enhancements would benefit all Moveworks customers, particularly those with small teams with limited resources and those who have not implemented the Data API.One example I would like to share is we are working an effort to correlate a potential decrease in the number of HR cases opened by new hires, and user engagement with the ‘Welcome to NG’ Edison nudges we deployed in August of last year. We are tracking the nudges that are sent via ServiceNow table, which does not capture if the user interacted with the message or not. 3,257 users who have received 14K+ ‘Welcome to NG’ notifications since the launch of this effort - I have submitted a request to our Customer Success team to see if they can pull a report of the 3K user interactions so we can manually review and see if they did/did not interact with the nudges. From the Moveworks perspective, instead of customers having to make these type of requests, the enhancements mentioned will empower self service by Moveworks customers and allow for them to easily capture the metrics they are interested in.