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.

[Ankur Bawiskar]

@Aparna45 

My thoughts

1) prevent users access to problem.do

-> you can't control this as user can type this in left nav

-> try to use onLoad client script on problem table and see what's in URL, if it contains particular pattern then use this script to make all fields readonly and use DOM manipulation to hide the Submit button.

2) New state and 1 problem per incident

-> use UI policy to make field editable and mandatory based on State field

-> use before update/insert BR on incident table and see if the problem_id currently present is already associated with some other incident. if yes then abort the operation

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏