Create Problem Task ui action is not working in service operation workspace(SOW)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
9 hours ago
Hi Team,
When clicked on create new Problem Task Ui button in SOW from Problem record there should be 2 options Root cause analyses and General .However, these options are not visible . Please find the attached screenshot for reference. Could someone please help me on this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
this table holds the interceptor values "sn_sow_interceptor_record_type_selector"
See if the records for problem_task are active or not
In my PDI those are active
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi @RamireddyD,
you mentioned a screenshot but there's not any, could you possibly add one?
100 % GlideFather experience and 0 % generative AI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2m ago
Hello @RamireddyD
My suggestion would be to first understand how you get below screen when you click "Create Problem Task" UI Action within a Problem Record in Service Operations Workspace (SoW):
Comparison of below between your PDI and actual Instance:
1. Table Name: sys_declarative_action_assignment with Filter as Action label is Create problem task
2. Ensure the related list of Action Assignment "sow_create_problem_task" is same as of PDI in your instance:
3. Open the record in the "Specify client action" field
4. Ensure Action Payload Definition "FORM_CREATE_PROBLEM_TASK" and it's related list in your PDI is same as of your instance:
I would also recommend to play around your PDI to modify like active to false, update pageTitle etc. to understand the changes to fully understand this functionality as it will help you identify the root cause in your instance.
Hope that helps!
