Skip to content

Commit d5d35df

Browse files
Update readme.md
1 parent 37b5bf2 commit d5d35df

File tree

1 file changed

+31
-1
lines changed
  • Client-Side Components/Catalog Client Script/Incident Sentiment Detector (Using Simple Word Matching, No AI)

1 file changed

+31
-1
lines changed
Lines changed: 31 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,31 @@
1-
Automatically classify the sentiment of an incident’s description (positive, negative, neutral) based on keyword analysis — no ML or API needed.
1+
Incident Sentiment Detector (No AI, Pure JavaScript)
2+
3+
A lightweight ServiceNow utility that detects sentiment (Positive / Negative / Neutral) of an Incident’s short description or comments using simple keyword matching — no AI APIs or external libraries required.
4+
5+
Useful for support teams to auto-tag sentiment and analyze user frustration or satisfaction trends without expensive integrations.
6+
7+
🚀 Features
8+
9+
✅ Detects sentiment directly inside ServiceNow
10+
✅ Works without external APIs or ML models
11+
✅ Instant classification on form update
12+
✅ Adds detected sentiment to a custom field (u_sentiment)
13+
✅ Simple to extend — just add more positive/negative keywords
14+
15+
🧩 Architecture Overview
16+
17+
The solution consists of two main scripts:
18+
19+
Component Type Purpose
20+
SentimentAnalyzer Script Include Processes text and returns sentiment
21+
Client Script (onChange) Client Script Calls SentimentAnalyzer via GlideAjax on short description change
22+
🧱 Setup Instructions
23+
1️⃣ Create Custom Field
24+
25+
Create a new field on the Incident table:
26+
27+
Name: u_sentiment
28+
29+
Type: Choice
30+
31+
Choices: Positive, Neutral, Negative

0 commit comments

Comments
 (0)