Create a catalog item that generates an existing standard change template and then generates catalog tasks once the standard change is completed

terrieb
Tera Guru

So need some assistance please.  After searching this forum, I thought I found the correct way to build a workflow that would generate first a task from the Change Request table using the template action and selecting the correct standard template through the search icon.

While it does generate a Change Request record, and has the fields filled in like the Standard existing template, it generates it as a Normal change and no workflow (no state is populated in the form and none available to select)

Am I missing a step?

Below is the screen shot of the workflow, the Create Task and the view of the "created" normal change record with no state selections available:

find_real_file.png

find_real_file.png

find_real_file.png

 

 

2 REPLIES 2

Dan O Connor
ServiceNow Employee
ServiceNow Employee

Hey. I think this is a common misconception I come across with Standard Changes.

You won't find an OOTB action in Flows for creating a Standard Change, whereas they exist for Normal and Emergency. This is because we collect Standard Changes into a catalog and category already. 

While by default the Standard Change Catalog is available for ITIL users, there is nothing to stop templates being made more available for staff.

I imagine the reason you are doing this, is because you want to provide users who are not within IT, the ability to raise these standard changes? 

a) If the userbase for requesting these changes is within IT, the Standard Change Catalog already exists, and that should be used.

b) If the userbase for requesting these changes is not within IT, add 'Available For' related list to Standard Change category in catalog, and add relevant usergroups. 

 

Creating a catalog request that goes into standard change isn't something that I'd recommend, or I've ever really seen work well. I think we forget Standard changes go into it's own catalog category, and therefore we can control providing it directly to users. 

This will be used internally by IT Staff only and use and existing Standard Change Template

So how to I "call" this template without using the Change Request Table in the Task and ensuring that after I select the template within the task, that it creates a Standard, not a Normal one?

I tried changing that to a Requested Item table, but all that did was create another Requested Item record, not a Change Request Record.

Am I open to build in Flow Designer if that is an easier route, but need guidance on how to build that.  I tried and it didn't create the Standard Change either....

 

Thanks