major incident state is set to "Rejected," the system automatically generates a problem record

monishasp
Tera Contributor

When the major incident state is set to "Rejected," the system automatically generates a problem record with a message like "Problem PRB0040058 is created for this Incident." How can I trace the workflow responsible for this? Essentially, I want to prevent the creation of a problem record when a major incident is rejected. I've checked all business rules but haven't been able to find the source of this problem record creation.

1 ACCEPTED SOLUTION

Ramya V
Kilo Sage

Hi @monishasp ,

There are Subflow, Playbook and Action in the flow designer which are responsible for creating problem record.

Subflow: [Non-ML] Create problem record for a major incident

Action: Create Problem Record from Incident

Playbook: Major Incident Process

Additionally there is a flow using the above mentioned action but by default it is in Draft not yet Activated.But this is when Major incident is accepted i.e., Flow: Create Problem from Major Incident

Steps to Check the OOTB Major Incident Process Playbook:

1. Open the Major Incident Process playbook.

2. Navigate to Step 8: Create Problem Properties.

3. In the Inputs section, you can view the conditions.

Screenshot 2025-03-20 at 6.37.17 PM.png

4. These conditions are defined in Step 1: Conditions Setup, where you can see three conditions: Close Conditions, Cancel Conditions, and Skip Conditions.

Screenshot 2025-03-20 at 6.41.23 PM.png

5. Click on Modify Condition to check or update the condition. For example, to check Problem Creation when the Major Incident State is Rejected, click on Modify Condition next to Cancel Condition. The OOTB conditions are defined as shown in the screenshot.

Screenshot 2025-03-20 at 6.44.30 PM.png

 

Please mark this answer as Helpful if this solution works for you.

View solution in original post

5 REPLIES 5

KirilD
Tera Contributor

I think there is a bug in the OOB Playbook for MI - even with proper conditions set for Cancel, the result is: the rest of activities in the Playbook are cancelled (cards in SOW), but the Create problem sub-flow is still executed. I created totally customized Playbook, activity definition and sub-flow with condition to check if MI state is not Accepted, then end the sub-flow.