Creating a new conflict status

[Nilanjan1]

Dear Experts, 

We are creating a new conflict state in the conflict table stating " In the Maintenance Window*.  Not sure whether someone has tried to create this as a custom state OR as a conflict entry... I tried creating a property and putting this the change conflict category but could not find much as a resource from other conflict states which can be used as a reference to create the new state. 

Any help is appreciated- 

[Dr Atul G- LNG]

Hi @Nilanjan1 

I'm not entirely sure about your exact use case, but from a process perspective:

• A conflict is a conflict—whether it's with another change, outside the Blackout Window (BW), or within the Maintenance Window (MW).
• If a change conflicts with another change and falls within the MW, how will the system determine which status to display?
• Additionally, this process isn't straightforward, as background scripts run to validate these scenarios.
• Each time the change form loads, the conflict check runs, adding another validation layer. Considering this, I suggest revisiting this request.

[Roger11]

We were looking to create a new "conflict type" by adding a new choice to the "type" field on the conflict table.

The way we ended up implementing this was to modify the script include "ChangeCheckConflicts" and to override the "check" function.

    check: function() {

        ChangeCheckConflictsSNC.prototype.check.call();

        // follow the OOTB conflict process with our custom ones where applicable.

        // Service Impacting Incidents for Change Model Changes.

        var _allowed_models = gs.getProperty(ChangeCheckConflicts.CHANGE_CONFLICT_SI_MODELS).split(',');

        if (_allowed_models.indexOf(this.sourceRecord.chg_model.toString()) != -1) {

            this._check_service_impacts();

        }

    },

in the called module, we check for the impact scenario, check that an existing conflict isn't present of the same type etc and if not, create the conflict there. There's not much info available in this space and the conflict code is extensive and not easy to wrap your head around.

If anyone has potential improvements to this approach...keen to hear.