Skip to main content

    Filter by idea status

    Filter by product

    1344 Ideas

    gsachdevNew Participant

    Ingest ServiceNow Content Management news articles as a native knowledge source in Moveworks1. New

     OverviewMoveworks currently supports ServiceNow Knowledge Bases as a native data source for AI-powered responses. We'd like to propose extending this native ingestion capability to also include pages and news articles published through the ServiceNow Content Management System (CMS).Problem Statement Organizations frequently use ServiceNow CMS to publish important internal news, announcements, etc that are separate from structured Knowledge Base articles. Today, this content is not surfaced by the Moveworks bot, meaning employees receive incomplete or outdated answers — especially during organizational changes, system outages, or rolling news updates where CMS articles are the authoritative source. We'd like Moveworks to natively ingest ServiceNow CMS content (news articles, landing pages, topic pages) in addition to existing Knowledge Base ingestion — with the following capabilities:Native connector: Treat CMS pages/articles as a first-class source alongside Knowledge Base articles in the Moveworks data ingestion pipeline. Configurable scope: Allow admins to select which CMS categories, topics, or content types to include/exclude. Freshness sync: Respect publish/unpublish dates so the bot only surfaces active, non-expired articles. Attribution: Surface the article title and CMS URL in bot responses, consistent with how KB articles are cited today.Expected OutcomeBot AI responses become more accurate and timely by incorporating the full breadth of published internal content from ServiceNow — not just structured KB articles. Employees get one consistent answer source rather than being told to "check the intranet separately."IT, HR, and Communications teams who publish CMS-first content and want that content reflected in Moveworks AI responses without manual duplication.

    Indrashis
    IndrashisCommunity Manager

    Troubleshooting Hub: Content2. On Roadmap

    What’s changing?Moveworks is introducing a dedicated Content experience in the Troubleshooting Hub within Moveworks Setup. It will bring content health, record-level troubleshooting, and access investigation into one customer-facing experience.The Troubleshooting Hub will help admins and implementation partners understand whether content and permissions are syncing correctly, identify customer impact, and resolve issues without navigating multiple tools or interpreting internal ingestion processes.The experience will include:Content health at a glance: Review synced and failed record counts across the organization and individual content sources.Source-level monitoring: Understand whether a newly configured source is scheduled, progressing normally, active, or affected by an issue.Impact-based issues: See clear explanations of problems such as blocked first syncs, stopped updates, stale permissions, or unavailable content.Record-level troubleshooting: Search content and understand whether each record is synced, stale, or failed, including the relevant reason and freshness information.Check Access: Test whether a specific employee can access a specific record and understand the identity, group, permission, audience, and access-rule decisions behind the result.Guided resolution: Review the affected scope, likely cause, recommended actions, ownership, and the checks needed to confirm recovery.These changes are designed to help admins and partners detect content and access issues earlier, understand their impact, and resolve common problems with less reliance on Moveworks Support.