- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2025 06:24 AM - edited ‎01-08-2025 06:27 AM
There is a true/false field (known_error) on the problem table in SN, but it does not seem to be related to any functionality. I don't know if I recall correctly but that field used to be visible on the Problem ticket form, maybe under certain conditions, but currently it does not seem to have any purpose. Has that field and related functionalities been removed in one of releases? In the demo data, there is one Problem record which has this value set to true and I was wondering whether there is anything that changes the value of that field under some conditions.
Solved! Go to Solution.
- Labels:
-
Problem Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2025 07:01 AM - edited ‎01-08-2025 07:15 AM
Hi @Pawel Czubak,
It's an interesting question and something that I believe is a legacy field. I see no Business Rules or Script Includes etc that call or reference it on an initial review and dig.
For context, pre Madrid 'Known Error' was a state value within the Problem Lifecycle, however from Madrid onward and for new customers, that state was removed and a newer process and state values were introduced.
You'll also notice that a 'Create Known Error' UI Action was also made available whereby a Knowledge article is created and then tied back to the problem.
See Create Known Error on the docs:
Point to note - just because a Knowledge article is created and linked to a Problem, unless the Knowledge base is configured correctly as a Known Error, this is where the flag may come into play, but this really is dependent on how your instance and importantly how Known Errors and your Knowledge Bases are configured.
To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2025 07:01 AM - edited ‎01-08-2025 07:15 AM
Hi @Pawel Czubak,
It's an interesting question and something that I believe is a legacy field. I see no Business Rules or Script Includes etc that call or reference it on an initial review and dig.
For context, pre Madrid 'Known Error' was a state value within the Problem Lifecycle, however from Madrid onward and for new customers, that state was removed and a newer process and state values were introduced.
You'll also notice that a 'Create Known Error' UI Action was also made available whereby a Knowledge article is created and then tied back to the problem.
See Create Known Error on the docs:
Point to note - just because a Knowledge article is created and linked to a Problem, unless the Knowledge base is configured correctly as a Known Error, this is where the flag may come into play, but this really is dependent on how your instance and importantly how Known Errors and your Knowledge Bases are configured.
To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie