What is the best way to auto-create tasks (each with different layout) on a Change Record?

[frappe]

When my user creates a change request I want it to be pre-populated with change tasks.

Each Task will have different fields on it depending on what the task is for.

What is the best way to do this?       I tried using an Execution plan but if I change a task it's changing all tasks.  

How do I create specific kinds of tasks and yet have them auto-populated with the Change is created?

Thanks !

[Pradeep Sharma]

Hi Kristin,

You can create a workflow and then use activity "Create Task" to create the task. Please refer OOTB workflows on change request for reference.

http://wiki.servicenow.com/index.php?title=Workflow_Concepts

http://wiki.servicenow.com/index.php?title=Task_Activities#Create_Task

[Chuck Tomasi]

Hi Kristin,

Are you looking for different form layouts for each type of task? If that's the case, you can use Views and View Rules to determine what to display and when.

View Management - ServiceNow Wiki

Alternatively, you could potentially use UI Policies to show/hide fields depending on other field values.

Creating a UI Policy - ServiceNow Wiki

Let me know if I did not understand our requirements properly.

[frappe]

Yes, different form layouts and fields for each task. For example I don't want to see Configuration item of Affected CI's on some tasks but I do want to see it on others.   Sounds like there are a couple options.   What I was really hoping for though was rather than show/hide stuff I could create my change tasks and configure them with whatever format and fields I needed, create my execution plan based on these tasks and whenever I create change type X the change is created with my adorable tasks on it.       Is there a way to do that without customization or is show/hide the only way (best way) to do this?

[Chuck Tomasi]

Hi Kristin,

There's no easy way to say "I want this task with layout A and that task with layout B" unless you first define what those layouts are and apply rules that depend on the data. Otherwise configuring ServiceNow would be widely more complex and inconsistent and of course, confusing to the people using it. "Why is this field on the left in this screen, but on the right on that other screen!" Ouch!

What you want is possible, it just take some planning and execution with consideration for the users.