create a new Major Incident from SOW through tab (+) / UI Action

[Fariya Muskhan]

Hi,

I’m attempting to add a new workspace tab option that allows users to create a Major Incident by updating the Chrome Tab JSON property. However, I’m unable to set the Major Incident state to “Accepted” through the JSON configuration.

I also tried invoking the MIM Major Incident Template via the same JSON configuration, but that approach is not working either.

Could you please confirm whether this is possible through the Chrome Tab JSON object? If it isn’t supported, what is the recommended approach—such as using a UI Action—to create a Major Incident and automatically apply the required state/template?

Thanks in Advance!!

[pr8172510]

Hi Fariya,

The chrome_tab JSON (newTabMenu) lets you add a "New Major Incident" option and pre-fill some fields via query parameter, but setting major_incident_state=accepted directly on creation often doesn't work. Same with calling the MIM template — the field has special processing in Major Incident Management, so it doesn't behave like normal fields.

Recommended approach:

Create a UI Action on the Incident table. This is cleaner and more reliable for auto-setting the state + applying the template.

var inc = new GlideRecord('incident');

inc.initialize();

// Basic details

inc.short_description = "Major Incident created from Workspace";

// Set Major Incident fields

inc.priority = 1;

inc.impact = 1;

inc.urgency = 1;

inc.state = 2; // State = Accepted (verify value in your instance)

inc.major_incident_state = "accepted";

var newSysId = inc.insert();

// Open new record in workspace

action.openGlideRecord(inc);

[pr8172510]

[Fariya Muskhan]

Thank you for your response.

Instead of inserting the record directly, would it be possible to open a new incident form with the required fields- such as impact, urgency, and priority, pre-populated, while also applying the Major incident template or appropriately setting the major incident state?

Our requirement is for users to review and complete the remaining mandatory fields before saving the record, rather than having the major incident created automatically.

[lauri457]

This is what your chrome_tab property should look like if you want to apply filters to new records from the tab creation.

{
    "contextual": [
        "record",
        "kb_view"
    ],
    "newTabMenu": [
        {
            "label": {
                "translatable": true,
                "message": "New major inc"
            },
            "routeInfo": {
                "route": "record",
                "fields": {
                    "table": "incident",
                    "sysId": "-1"
                },
                "params": {
                    "query": "major_incident_state=accepted"
                },
                "multiInstField": "sysId"
            },
            "condition": {
                "tableDescription": {
                    "table": "incident",
                    "canCreate": true
                },
                "roles": [
                    "major_incident_manager"
                ]
            }
        }
    ],
    "maxMainTabLimit": 10,
    "maxTotalSubTabLimit": 30
}

You also need to get rid of this attribute on the mim state in the sys_dictionary record. Note that after you remove this then it can applied through the filter (accidentally) when clicking new on a list.

Although I'd question the need to have such convenient access to major inc creation anyway.  The platform is heavily steering you towards the proposal/promotion process. MIM is not for the average p1 incident but a separate process for catastrophic incidents