As a Problem Process Owner, I do not want users to create a problem using this problem.do

[Aparna45]

We follow the out-of-the-box Problem Management process, where problems must be created only from incidents. However, accessing problem.do allows users to bypass this and create problems without an associated incident.

Proposed Options:

1. Prevent access to problem.do

2. In the “New” state, make First Reported By editable and mandatory. After moving out of the “New” state, this field should become read-only. Also ensure that only one problem can be created per incident.

Any guidance or suggestions would be greatly appreciated.

[Its_Azar]

Hi there @Aparna45 

You can handle this easily by preventing direct creation via problem.do. The best approach is to add a before insert Business Rule that checks if the First Reported By Task (linked incident) is empty — if so, abort creation with a message. You can also make the First Reported By field mandatory and editable only in the New state using a UI Policy, and read-only afterward. and, add a check to prevent multiple problems for the same incident.