/
/
Record the root cause on a ServiceNow problem in one step
For problem managers who want the cause written up, the state moved on and the analysis task closed in ServiceNow, by asking their AI assistant.
On this page
Connector
Connect ServiceNow, pick your AI tool and paste the prompt.
The problem
Root causes stuck in someone's notes
Once a problem's cause is found, it needs to be written onto the problem, the state moved on and the analysis task closed. Done separately, the cause sits in someone's notes and the investigation task stays open for weeks.
Without PopdockAI
- Update the problem fields by hand
- Move the state forward separately
- Forget to close the analysis task
- Lose the cause in personal notes
With PopdockAI
- Resolved or closed problems stop the job
- The new state, notes and tasks to close are shown first
- The cause is recorded and analysis tasks closed after you confirm
- Both are re-read, and no resolution code is set early
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Record the root cause `{cause-notes}` and workaround `{workaround}` on problem `{problem-number}`, move it to Fix in Progress, and close its root cause analysis task.
**Step 1: Read the problem and its tasks**
* Call `servicenow-get-problem` with number `{problem-number}`. Keep sys-id, state and assigned-to. If it is Resolved or Closed, stop.
* Call `servicenow-get-problem-task` with problem `{problem-number}`. Pick out open tasks of type Root cause analysis and keep their sys-ids.
**Step 2: Confirm**
Show: the problem, current state, new state Fix in Progress, the cause notes, the workaround (or "none"), and which RCA tasks will be closed. Ask for an explicit yes.
**Step 3: Write**
1. Call `servicenow-update-problem` once with sys-id, cause-notes `{cause-notes}`, workaround `{workaround}` only if given, state Fix in Progress, and work-notes "Root cause recorded."
2. For each open RCA task from Step 1, call `servicenow-update-problem-task` once with its sys-id, cause-notes `{cause-notes}`, state set to the closed-complete value the tool lists, and a close-code if the tool requires one (ask the user if unsure).
**Step 4: Verify and report**
Re-read with `servicenow-get-problem` and `servicenow-get-problem-task`. Report the new state and which tasks closed. If a workaround was given, suggest running draft-knowledge-from-problem so the service desk can find it.
**Rules & Guidelines:**
* Write tools allowed: `servicenow-update-problem` once and `servicenow-update-problem-task` once per open RCA task, after one confirmation. Do not touch non-RCA tasks and do not call any add- tool.
* Do not set resolution-code here; the problem is not resolved until the fix is in.
**Validation:**
* If there is no open RCA task, update only the problem and say so.Who it's for
One answer, three teams that use it
Problem managers
Move problems forward cleanly
Record the cause, change the state and close analysis tasks in one confirmed step.
Record the root cause on PRB0040311: an expired certificate on the load balancer.
Infrastructure engineers
Write up what you found
Put the cause and workaround on the problem straight after the investigation.
Root cause for PRB0040287 is a memory leak in the print service. Workaround: restart nightly.
Service desk leads
Share causes with the desk
Make the cause visible to agents handling related incidents.
Update PRB0040350 with the root cause: DNS record pointing at the old server.
How it works
What PopdockAI does when you ask
You give the problem and its root cause, and your AI assistant prepares the updates. The problem and its analysis tasks change only after you confirm.
01
Ask
You give the problem number, the root cause and optionally a workaround.
02
Read
It reads the problem and its tasks, stopping if already resolved or closed.
03
Confirm
You see the new state, notes and the analysis tasks to close, and say yes.
04
Update
It records the cause, closes the analysis tasks and re-reads both.
What PopdockAI provides
The tools behind the answer
Ready made tools for ServiceNow and one secure connection to your AI tool. No code, no exports.
servicenow-get-problem
servicenow-get-problem-task
servicenow-update-problem
servicenow-update-problem-task
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Root causes recorded where everyone can see them
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
