Ingested Files (New)

Resource Lifecycle

After connecting Moveworks to your content system (like ServiceNow, Confluence, Google Drive, etc) and setting up ingestion, raw records (files, knowledge articles) are pulled in. These records then undergo processing and validation before being indexed in Moveworks and made available for serving.

Purpose of New Ingested Files Screen

Ingested Files Screen serves following use-cases for admins:

• Connected systems health: Monitor health of connected systems by reviewing whether Moveworks is able to successfully crawl and ingest files from your connected systems
• UAT of newly configured system: Validate if content is getting successfully ingested and indexed into Moveworks. Additionally validate if the count of ingested and serving records from your newly configured system is as per your expectation or not
• Periodic checks on key metrics: Keep periodic checks on ingested records, serving records, and non-serving records. Act swiftly on any deviation on these metrics
• Troubleshooting: Identify and resolve issues such as unhealthy systems, failed ingestion runs, permission ingestion failures, lower than expected file counts, missing files, files not serving to users, and file-level issues

Comparison: New and Legacy Interfaces

The updated ingested file screen comes with new capabilities including:

• Visibility into content and permission ingestion status
• View of total files ingested, serving files, and not serving files
• Ingestion and indexed timestamps details
• Permission ingestion status for each file
• Filtering and enhanced search
• Redesigned UI/UX

These improvements give Moveworks admins a comprehensive view of content imported from external systems and make content troubleshooting easier and more effective.

New View

Legacy View

New Ingested Files Screen Components

Ingestion Health Widgets

• Content Ingestion: Monitor file ingestion systems' health, view ingestion runs with logs, schedules (full and incremental), and error summaries, and quickly access connector and ingestion configs
• Permission Ingestion: Monitor permission ingestion systems' health, view ingestion runs with logs, schedules (full and incremental), and error summaries, and quickly access connector and ingestion configs

Read more about Data Ingestion: Data Ingestion View

Ingested Records Widgets

• Ingested Files: Count of unique files crawled and ingested
• Serving Files: Count of unique files successfully processed and ready to serve to users
• Not Serving Files: Count of unique files that failed to process and are not currently serving to users

Ingested Records Table

• Last Indexed At (Table Header): Timestamp when the index was last updated (based on latest fetched file)
• External Record ID: The unique ID of a file fetched from your external system
• Title: The title of a file fetched from your external system
• Content Status: Whether a file is currently serving or not serving
• Connector: Name of the connector from which a file is ingested
• Permission Ingested: Whether permissions are ingested for a file from the external system (true/false)
• Last Ingested At: Timestamp when the content was last ingested
• Last Indexed At (Table column): Timestamp when a file was last indexed

🚧

Important Note: Ingested and Indexed timestamps may differ

When ingestion happens, there might be no updates to existing content. If no changes are found, the index is not updated.

Filters

• External ID: Filter files by their unique ID from the external system to quickly locate specific files
• Content Status: Filter files by their current status (Serving or Not Serving) to identify files available to users or troubleshoot issues
• Connector: Filter files by the connector source to view files from specific connectors (e.g., Google Drive, Box, SharePoint)

📘

Important Tip

You can combine multiple filters to narrow down results and find exactly what you're looking for.