normal changes model records

[LadySGRho89]

Is it possible for regular ITIL users to create their own model changes for normal changes? For example, someone wants to create a model they can use each month for monthly patching that would include their entire list of CIs. Also, is there a way to do a bulk import of CIs from a spreadsheet?

[pablo_itguy_pl · Accepted solution]

Have you consider fulfilling this scenario by using templates. Change template can be created for patching use case (prepopulating all "common" fields) - so this would speed up change record creation process.

For bulk CI import I'm assuming adding multiple CI as Affected CIs to change record with quick step:

- use Add button on "Affected CI" related list

- modify the filter to sth like Name - is one of and copy list of CI names from excel

- for filtered list just Add All

[pablo_itguy_pl · Accepted solution]

[pablo_itguy_pl · Accepted solution]

Hello,

If you need to stick with OOB (without any customizations/enhancements) I would go with Conflict detection which is already implemented in the tool.

Example from my PDI instance:

1. I have a blackout window for every Wednesday:
2. 
3. Now I register new change request record and schedule it within blackout window. After save/submit I will have following warning on the screen:
4. 
5. I can review conflicts in two ways: looking at Conflicts tab:
6. 
7. OR I can use Conflict Calendar
8. 
9. 

By building detailed Standard Operating Procedures / Work Instructions and utilizing OOB functionality you should be able to manage this perfectly.

[LadySGRho89]

I have to say, both of your solutions are spot on. Thank you so much as this was extremely helpful to me. BTW how familiar are you with backout windows. We are trying to configure our instance to give a pop up box when someone creates a change that is within a blackout window. We are using the OOB version so I have been told we need to pay for customization in order for this to work. Any suggestions??? And again, thank you so much.

[pablo_itguy_pl · Accepted solution]

Hello,

If you need to stick with OOB (without any customizations/enhancements) I would go with Conflict detection which is already implemented in the tool.

Example from my PDI instance:

1. I have a blackout window for every Wednesday:
2. 
3. Now I register new change request record and schedule it within blackout window. After save/submit I will have following warning on the screen:
4. 
5. I can review conflicts in two ways: looking at Conflicts tab:
6. 
7. OR I can use Conflict Calendar
8. 
9. 

By building detailed Standard Operating Procedures / Work Instructions and utilizing OOB functionality you should be able to manage this perfectly.

[LadySGRho89]

You are amazing. One last question, how can I set up my CAB workbench to include standard change templates? Right now, I run my CAB and review changes but I have to got to a separate window to pull up open standard templates. I was told there is a way to have them displayed in the CAB workbench but I cannot figure out how to do this. Thanks

[pablo_itguy_pl · Accepted solution]

Hi,

I'm assuming that you would like to have "Standard Change Proposals" included in items of CAB meeting.

You can modify your CAB meeting - manually add item to agenda:

[LadySGRho89]

THANK YOU VERY MUCH!!!