Can you add Affected CIs to a Normal Change Template

[Cirrus]

Hi,

Does anyone know if its possible to add the Affected CIs related list to a normal change template? I know it can be done for Standard Change Templates (see How to create a Standard Change template with multiple Affected CIs) 

In the absence of service mapping, I have a requirement for both standard and normal change templates to list multiple affected CIs which can then be pulled through to the related list on the change when the template is selected

Thanks

[Uncle Rob]

Normal, Standard, and Emergency are just text values in a choice list.  The solution you'd need is the same one you linked to.

[Cirrus]

Robert, perhaps I am not understanding you or I'm just having one of those moments!

The solution I pointed to relates to a standard change proposal and works perfectly. That proposal is then converted to a standard change template. All good so far. The problem comes when support teams create their own normal change templates, which dont go through a proposal phase and are created directly in the sys_template form which doesnt have an option to add Affected CIs as a related list.

Are you inferring that all templates should go through a proposal (in which case I agree with your response)? My concern is that we would end up with a change catalogue composed of both standard and normal proposals, but we need to keep the two separate.

Thanks

[Alikutty A]

Hello,

Have you checked the template feature for related records? You can get your exact requirement applied using the related templates option.

The SN documentation gives us a good example on its usage. In the sample explained, You need to just replace change tasks with your affected CI record templates and you should be good.

Please check here

Thanks!

[Cirrus]

Helpful as always Ali, but I think at this point we need to walk away because of the following: 

Note: Child templates can only be applied automatically if you first apply the parent template from a module.

If I am understanding correctly, we would need to create child templates for each service with Affected CIs, then relate these to the parent template, then create a module for each parent template. Given that we have over 100 different service templates, this would make the navigation menu impossible to navigate. Looks like we need to get a move on with service mapping!!