Standard Change Catalog - How to create change tasks from proposal?

[tee3]

Hello all,

We are planning to implement the Standard Change Catalog in our Helsinki instance and I'm looking for some ideas/suggestions on how to allow users to create templates for change tasks within the change proposal.

Our organization has very specific and detailed tasks within these standard changes that can be assigned to different assignment groups and what we want to be able to do is allow users to submit a proposal with information for the change request, change tasks and affected CIs within this proposal that will then convert into a standard change template they are able to use to create changes.

How have you implemented standard change catalog in your environment? Suggestions and ideas are welcome.

Appreciate it!

[Dominik Simunek]

Sorry for the delay. Below is the more detailed description.

[olivierb_]

Hi Dominik,

I'm not the one who started this thread, but I'm also interested to have more info about what you did, because I have the same exact need as tee.

Could you share some details about the method to implement?

Thanks for your help.

Regards,

Olivier

[Dominik Simunek]

Hi Olivier, Adarsh,

I will try to explain here in more detail:

1) Create new table for Change Task Template/Proposal - this table needs to have either field of type "Template values" or should be extended from Template table. So that you can define template values for the change task in the same way as for Standard Change Proposal.

2) Add reference to std_change_proposal so that these two tables are linked.

3) Add related list of Standard Change Task Template table to the Standard Change Proposal form (notice you will be able to define change task templates on the form of proposal, not in the record producer "Propose a new template...").

4) Create a business rule (after insert on change_request if "Standard Change Template version" is not empty). Write a script to do - a) querying task templates and b) creating a change task for each using applyEncodedQuery to apply the template value and link it to the change request.

5) Optional - if you want to know that a Change Task was created by a template, create additional field "u_std_change_task_template" and set it in BR above to the task template so that reference to it is stored. You can then have special logic e.g. not allowing to delete these templated tasks, but allowing to delete those additional created for a standard change by a user. Or e.g. making fields defined in the template read-only.

That's I guess all you need to do. The bad thing on this implementation is that change task templates are linked to a proposal and so once you want to modify a template by creating new proposal, you would need to copy those task templates to new proposal or leave user to re-create them again.

Hope this helps to get the idea. Regards.

Dominik

[olivierb_]

Thanks Dominik,

It's a bit more clear to me.

I will give it a try today and post an update to this post with a fully detailed step by step procedure if I manage to make it work as I want.

Thanks for your help.

Regards,

Olivier

[tee3]

Looks like this is no longer an issue in Jakarta! Just thought I'll update the thread, in case anyone was still looking into this and has not already implemented the solution proposed by Dominik.

https://docs.servicenow.com/bundle/jakarta-it-service-management/page/product/change-management/task...