Good afternoon.
How does PRB (Problem) get automatically created by system once a Major Incident gets closed?
Is there any rule Business rule or something? Please help.
The issue is, we also have once more Business rule for the same issue, but one more is conflicting with it, and sometimes 2 PRB records are getting created: one by system and other by Business rule.
My requirement is: to copy the Major Incident field's data to PRB, once the Major Incident gets closed.
(I actually turned off my business rule and again tried closing the Major incident, but still PRB was getting created, by somewhere.)
@Ankur Bawiskar @Dr Atul G- LNG
I answered it earlier
Automatic problem record is getting created when M1/M2 incident getting resolved
it comes from this playbook "Major Incident Process", You can see after Resolve step, it's creating Problem Record
In the Step 8 it calls this "Major Incident Playbook - Create a Problem from Incident" subflow
This subflow calls another flow action "Create Problem Record from Incident" where the problem is created
1) Subflow
2) Action
If my response helped please mark it correct and close the thread so that it benefits future readers.
it comes from this playbook "Major Incident Process", You can see after Resolve step, it's creating Problem Record
In the Step 8 it calls this "Major Incident Playbook - Create a Problem from Incident" subflow
This subflow calls another flow action "Create Problem Record from Incident" where the problem is created
1) Subflow
2) Action
1) either deactivate that subflow
OR
2) Remove that Step 8, remember you will have to update the playbook in the correct scope
OR
3) Update that flow action
it comes from this playbook "Major Incident Process", You can see after Resolve step, it's creating Problem Record
In the Step 8 it calls this "Major Incident Playbook - Create a Problem from Incident" subflow
This subflow calls another flow action "Create Problem Record from Incident" where the problem is created
1) Subflow
2) Action
1) either deactivate that subflow
OR
2) Remove that Step 8, remember you will have to update the playbook in the correct scope
OR
3) Update that flow action
