For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
      • How to Configure Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • Step 1: Navigate to Ticketing > Ticket Interception
  • Step 2: Configure the DSL Rule for Each Plugin
  • Step 3: Set “Enable ticket interception on NGCP” to True
  • Step 4: Lastly, navigate to ticket filters and configure a filter to ensure only the desired ticket types are eligible for ticket interception.
Service ManagementTicket Interception

How to Configure Ticket Interception

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Generic Ticketing Integration: Ticket Gateway

Next
Built with

Step 1: Navigate to Ticketing > Ticket Interception

This page will contain configurations for each Plugin that is supported for ticket interception


Step 2: Configure the DSL Rule for Each Plugin

Input a DSL rule for each functionality you would like to enable ticket interception for. Enter True to enable ticket interception for all users for that feature.

Note: To enable ticket interception for a few select users you can leverage a DSL rule. For example, the following rule enables the features for only 2 users: (1) email1@example.com and (2) email2@example.com

user.email_addr IN ["email1@example.com", "email2@example.com"]

Note: DSL Rules are case sensitive, so ensure the email addresses are lowercase.

Step 3: Set “Enable ticket interception on NGCP” to True

This configuration is the top level on/off switch for Ticket Interception. Users must pass both this rule, and the plugin specific rule for a ticket interception to trigger.

Step 4: Lastly, navigate to ticket filters and configure a filter to ensure only the desired ticket types are eligible for ticket interception.

All tickets that meet the criteria of the Filter for actionable tickets will be eligible for ticket interception.

IMPORTANT Testing Instructions

When testing ticket interception, be sure to:

  1. File the ticket from your ITSM portal
  2. Set the requestor to a user different from the assignee of the ticket
  3. Ensure the state of the ticket corresponds to New status on Moveworks to ensure it is eligible for ticket interception.