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,

The only option I can think off is hide/show the field based on some logic(customization) via UI policy/client script

If you want to control it via view then you can create views and restrict it via role.

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

[Chuck Tomasi]

To be clear, the views don't HAVE to be restricted by role.

Change management comes with some great examples. If change type=Emergency, a specific set of fields is shown. If change type=Standard, a different set of fields is shown. That's the easiest case for view rules.

The situation with UI policies and client scripts is that you can load a form, but users will see it fully loaded, then "transform" in to something else. What's more, managing complex sets of "hide A when X and Y, but show B when NOT X and Y" can really get to be a mess.

Best practice for multiple complex form layouts is start with a view and tweak it with UI policies and client scripts.

See section 4 here. Modifying the Application Design - ServiceNow Wiki

[frappe]

Thanks for the info ... spent quite some time trying to figure out what I could do here.

Actually I do think this would be a good feature to have, especially for change management (and this would have way more value for linked release and it's changes).   I"m not thinking of having a field on one side here and another side there - I'm thinking bigger and wanting to make the user self-sufficient in the tool.  

Take a common set of sequential and/or parallel tasks in a Change Request:

Task 1) Create Request for Change (often a document to support html and review comments).   User creates this and attaches to the change request.     On this task I don't want configuration item or affected ci's but I do want one and only one UI Action reference right there on the task to link with the request for change template they will need (external url).

Task 2) Submit for approval that's assigned to change management.     I don't want to see a CI field or affected CI's on this task, I may want to see some custom fields here or references to different external URL's.

Task 3) Test Signoff - generic task probably fine

Task 4) Deploy to Production - generic task probably fine

Task 5) Customer Signoff -   don't want to display config item field or affected CI's, might want custom field info here.

Task 6) Post Implementation review - want custom fields related to PIR evaluation

-K

[Chuck Tomasi]

Hi Kristen,

Thanks for the details. All of what you want to do is possible and there are options to do it. We've highlighted a couple of the common ones - and since this IS a development platform, there are other many ways to accomplish the same task. 🙂

Due to limitations in the community, I'm not sure how much further we can take this discussion unless you have something specific you want to discuss.

If you feel you have a feature request/enhancement to the platform, I encourage you to visit this page.

Thanks

[frappe]

Hi Tomasi

No worries, thanks so much to both, you rock on response time.       You can close this discussion.   One of my guiding principles is absolutely no customization (configuration only) unless you have a really really good business case so I'll find a way.  

Thanks !