What can you do with a Matching Criterion in ServiceNow FSM?

What can you do with a Matching Criterion in ServiceNow FSM?

• A. Copy, rename, and configure for use against other tables
• B. Only view and delete
• C. Only apply to the Case table
• D. Requires coding

Answer: (A)

Matching Criteria define reusable rules that dictate how related records are found across tables in Field Service Management. They’re not a one-off setting tied to a single table; you can clone an existing criterion, rename the copy to reflect its new purpose, and adjust its configuration so it can be used with other tables. This means you can propagate the same matching logic to different FSM contexts without starting from scratch, all through the UI without writing code. That’s why copying, renaming, and configuring a Matching Criterion for use against other tables is the correct approach. The other options don’t fit because Matching Criteria aren’t limited to viewing or deleting, aren’t restricted to the Case table, and don’t require coding.

Matching Criteria define reusable rules that dictate how related records are found across tables in Field Service Management. They’re not a one-off setting tied to a single table; you can clone an existing criterion, rename the copy to reflect its new purpose, and adjust its configuration so it can be used with other tables. This means you can propagate the same matching logic to different FSM contexts without starting from scratch, all through the UI without writing code. That’s why copying, renaming, and configuring a Matching Criterion for use against other tables is the correct approach. The other options don’t fit because Matching Criteria aren’t limited to viewing or deleting, aren’t restricted to the Case table, and don’t require coding.