- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello ,
I am currently learning ServiceNow Problem Management and have a question regarding the process flow.
When a Problem record moves from the Assess stage to the Root Cause Analysis stage, should we create and complete any Problem Tasks before starting the Root Cause Analysis?
Or can we directly move the Problem record to the Root Cause Analysis stage and perform the investigation without creating any Problem Tasks?
I noticed that the Problem form has a related list called "Problem Tasks".
I would like to understand:
Are Problem Tasks mandatory before starting Root Cause Analysis?
What is the actual purpose of Problem Tasks in real-time projects?
In which situations should we create Problem Tasks?
Is it possible to complete Root Cause Analysis without creating any Problem Tasks?
Could anyone please explain the recommended real-time workflow?
Thank you!
Best regards,
Damodar.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Damodar,
Short answer: No, Problem Tasks are not mandatory out of the box before Root Cause Analysis, and yes, you can complete Root Cause Analysis without creating any Problem Tasks. You can move the Problem record directly from Assess to Root Cause Analysis and record the investigation, root cause, and workaround on the Problem record itself.
Problem Tasks are child tasks of a Problem, used to break the work down when it cannot be done by one person on the Problem record alone. Their real purpose is assignment and tracking: for example, asking a network team to check logs, a database team to review errors, or a vendor to confirm a defect, each with its own assignee, due date, and work notes, while the Problem record stays the single place where the overall analysis is consolidated.
So, create Problem Tasks when:
- Different teams or people need to work on separate parts of the investigation in parallel.
- A piece of work needs its own owner, due date, or approval.
- You need a clear audit trail of who investigated what.
Do not create them just to move the stage forward. In a simple case where one analyst can investigate and document the root cause, working directly on the Problem record is the recommended workflow. The only exception is if your organization has customized the Problem form or workflow to require Problem Tasks, in which case that is a local customization, not out-of-the-box behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @BURLED
Here is my comments on your query:
1. No, Problem Tasks are not mandatory out of the box (OOB) to move the main Problem record to the Root Cause Analysis stage or to initiate an investigation.
2. Problem Tasks are useful for breaking down an investigation into smaller, manageable activities when multiple technical teams (such as Database Administrators, Network Engineers, and Application Support) need to investigate different aspects of the problem.
3. Same as answer 2.
4. Yes, this is possible out of the box (OOB).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @BURLED ,
Problem Tasks are not mandatory before moving a Problem record from the Assess stage to the Root Cause Analysis stage. You can perform Root Cause Analysis directly on the Problem record without creating any Problem Tasks, unless your organization has implemented a specific workflow or business rule that makes them mandatory.
Are Problem Tasks mandatory?
No. Problem Tasks are optional. You can directly move the Problem record to Root Cause Analysis without creating any tasks.Purpose of Problem Tasks:
They help divide complex investigations into smaller activities and track them separately.When should you create Problem Tasks?
When multiple teams or individuals need to investigate different areas of the same problem.Can RCA be completed without Problem Tasks?
Yes. For simple investigations, you can perform RCA directly on the parent Problem record.
Hope this helps! If this resolves your issue, please mark the response as helpful and accept it as the solution.Regards,
Sandesh Powar
ServiceNow Rising Star
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Damodar,
Short answer: No, Problem Tasks are not mandatory out of the box before Root Cause Analysis, and yes, you can complete Root Cause Analysis without creating any Problem Tasks. You can move the Problem record directly from Assess to Root Cause Analysis and record the investigation, root cause, and workaround on the Problem record itself.
Problem Tasks are child tasks of a Problem, used to break the work down when it cannot be done by one person on the Problem record alone. Their real purpose is assignment and tracking: for example, asking a network team to check logs, a database team to review errors, or a vendor to confirm a defect, each with its own assignee, due date, and work notes, while the Problem record stays the single place where the overall analysis is consolidated.
So, create Problem Tasks when:
- Different teams or people need to work on separate parts of the investigation in parallel.
- A piece of work needs its own owner, due date, or approval.
- You need a clear audit trail of who investigated what.
Do not create them just to move the stage forward. In a simple case where one analyst can investigate and document the root cause, working directly on the Problem record is the recommended workflow. The only exception is if your organization has customized the Problem form or workflow to require Problem Tasks, in which case that is a local customization, not out-of-the-box behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @BURLED
Here is my comments on your query:
1. No, Problem Tasks are not mandatory out of the box (OOB) to move the main Problem record to the Root Cause Analysis stage or to initiate an investigation.
2. Problem Tasks are useful for breaking down an investigation into smaller, manageable activities when multiple technical teams (such as Database Administrators, Network Engineers, and Application Support) need to investigate different aspects of the problem.
3. Same as answer 2.
4. Yes, this is possible out of the box (OOB).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @BURLED ,
Problem Tasks are not mandatory before moving a Problem record from the Assess stage to the Root Cause Analysis stage. You can perform Root Cause Analysis directly on the Problem record without creating any Problem Tasks, unless your organization has implemented a specific workflow or business rule that makes them mandatory.
Are Problem Tasks mandatory?
No. Problem Tasks are optional. You can directly move the Problem record to Root Cause Analysis without creating any tasks.Purpose of Problem Tasks:
They help divide complex investigations into smaller activities and track them separately.When should you create Problem Tasks?
When multiple teams or individuals need to investigate different areas of the same problem.Can RCA be completed without Problem Tasks?
Yes. For simple investigations, you can perform RCA directly on the parent Problem record.
Hope this helps! If this resolves your issue, please mark the response as helpful and accept it as the solution.Regards,
Sandesh Powar
ServiceNow Rising Star