Default Category of Affected Configuration Items Field on Change Request

Nick_Flint

We are creating a change request from from New -> Work Item -> Change Request -> From Template -> Change Template screen. The Affected Configuration Items field defaults to the Configuration Items class. Is it possible to instead default this to a different class (e.g. Business Service)?

Nicholas_Velich

This is mostly possible out-of-box. To do so, add the following to your /CustomSpace/ChangeRequest.js file.

{

        name: "Business Services",

        type: "multipleObjectPicker",

        PropertyName: "RelatesToConfigItem",

        ClassId: "b2a806a6-87f6-0bc9-da74-c27e9ab5a5d7",

        PropertyToDisplay: {DisplayName:"DisplayName",LastModified:"LastModified"},

        SelectableRow: true,

},

This will cause only the Business Services class to appear in the pop-up window, as so:


Okay now for the two caveats:

1) The relationship used here is still Work-Item-to-Configuration-Item, so if there are non-Business-Services objects already linked, you will see them on the form itself (still not in the pop-up window). This isn't a problem if you restrict the areas in which an analyst can link a WI to a CI.

2) You cannot use this control in tandem with the canned-related-items picker, otherwise you will get an error. If you use the above, remove the below from the ChangeRequest.js file:

{

        name: "RelatedConfigurationItems",

        type: "relatedItems"

},

Thanks,
Nick

Nicholas_Velich

One more note, the above uses the "Work Item Relates to Config Item" relationship, but if you wanted to use the "Work Item Affects Config Item" relationship, replace the PropertyName above with "HasRelatedWorkItems"

In turn, you would need to make sure you are not using the following canned control:

{

        name: "AffectedConfigurationItems",

        type: "affectedItems"

},

Nicholas_Velich

@Nick_Flint Unfortunately, the search field directly on the form is part of the canned related/affected item controls, and isn't available as part of the multipleObjectPicker.

Konstantin_Slavin-Bo

Maybe you can edit something in the CR template, but I'm not sure which values are accepted here?

Peter_Settle

When you go to the Config Items to Change field, you just add the service there. It will probably default to Computer. This can be changed to whatever you wish to select, by searching for it. Business Service does appear in the list, therefore as long as you have some setup there should be no reason why you can not select them.

Nick_Flint

After  I looked at this again I realized that I can start typing the name of a Business Service and it will appear. The customer is asking to have that field ONLY display Business Services on the Change Request form. 

Konstantin_Slavin-Bo

I don't think this is possible OotB, as there's no built-in control for this on the portal. But I guess you could create your own field, which replaces the OotB field, where you make your own search criteria. You would have to use the /Search/GetObjectsByCriteria endpoint, setup the criteria to only include the Business Service class, and make sure to commit the selected CI to the CR. It's not impossible, but seems like a lot of work, for something that already is included in the current field

Nicholas_Velich

This is mostly possible out-of-box. To do so, add the following to your /CustomSpace/ChangeRequest.js file.

{

        name: "Business Services",

        type: "multipleObjectPicker",

        PropertyName: "RelatesToConfigItem",

        ClassId: "b2a806a6-87f6-0bc9-da74-c27e9ab5a5d7",

        PropertyToDisplay: {DisplayName:"DisplayName",LastModified:"LastModified"},

        SelectableRow: true,

},

This will cause only the Business Services class to appear in the pop-up window, as so:


Okay now for the two caveats:

1) The relationship used here is still Work-Item-to-Configuration-Item, so if there are non-Business-Services objects already linked, you will see them on the form itself (still not in the pop-up window). This isn't a problem if you restrict the areas in which an analyst can link a WI to a CI.

2) You cannot use this control in tandem with the canned-related-items picker, otherwise you will get an error. If you use the above, remove the below from the ChangeRequest.js file:

{

        name: "RelatedConfigurationItems",

        type: "relatedItems"

},

Thanks,
Nick

Nicholas_Velich

One more note, the above uses the "Work Item Relates to Config Item" relationship, but if you wanted to use the "Work Item Affects Config Item" relationship, replace the PropertyName above with "HasRelatedWorkItems"

In turn, you would need to make sure you are not using the following canned control:

{

        name: "AffectedConfigurationItems",

        type: "affectedItems"

},

Konstantin_Slavin-Bo

@Nicholas_Velich
That's pretty neat actually! Does this work with any type of class and relationship (which are valid in SCSM of course)? 

Nicholas_Velich

It does! The relationship is specified under "PropertyName" and the class that shows up in the pop-up is the "ClassId"

Konstantin_Slavin-Bo

That's cool and really nice to know, thanks a lot! 

Nick_Flint

@Nicholas_Velich Thank you for that! That is very helpful. 

Is having the search field on the form possible too? I'm thinking that functionality is why Affected Configurations Items is a canned field.

Nicholas_Velich

@Nick_Flint Unfortunately, the search field directly on the form is part of the canned related/affected item controls, and isn't available as part of the multipleObjectPicker.