🚀 Automating Task Plan Templates in ServiceNow: A Game Changer for FS Case Management

[Nick Daigneau]

Objective

This article provides more information on Task Plan Templates which are one of the most impactful features for streamlining case management in ServiceNow. As discussed in the video below, these templates allow process owners to predefine sets of tasks that can be applied to cases based on specific conditions, saving time, improving consistency, and enhancing visibility across workflows.

Note: This article was originally published in October 2025, when Task Plan Templates had to be invoked manually from the target record or triggered through a custom Business Rule. Several enhancements have shipped since then. Task Plan Templates now support automatic execution through a pre built flow action, template item dependencies, documentation support, and a rebuilt workspace authoring experience.

✅ Benefits of Task Plan Templates

• Accelerated case handling: automatically apply relevant tasks based on case type or attributes.
• Improved visibility: hierarchical task structures make it easier to track progress and dependencies.
• Scalability: easily adapt to changing business rules without manual reconfiguration.
• Empowered process owners: configure and manage task plans directly from the native workspace UI, without relying on admin level intervention or backend changes.
• Enforced sequencing: dependencies between template items control when each task becomes actionable, rather than releasing everything at once.
• Consistent reference material: a document attached at the template level propagates to every generated task, so agents work from one current version.

⚙️ Automatic Execution Without a Custom Business Rule

This is the most significant change since the original post. Task Plan Templates now ship a pre built Apply Task Plan Template action in Workflow Studio, published under the Task Plan Templates application. An admin can trigger template application from a flow, a subflow, or a Playbook stage, with no scripting and no Business Rule.

Previously, applying a template automatically meant either a developer writing a business rule or custom script, or an agent manually clicking a UI action on the case record.

Configuring it as an admin

1. Open Workflow Studio and create a new flow, or open an existing Playbook.
2. Add the Apply Task Plan Template action.
3. Select the template and map the source record.
4. Add any conditions the process needs around the action.
5. Activate the flow, or publish the Playbook stage.

What the process owner sees

The agent creates a case, either a standard case or a case type record such as onboarding, and the tasks are already there. No UI action, no button click, and no dependency on someone remembering which template applies.

Three details worth pulling out:

• The trigger is configurable in Workflow Studio, so task generation can fire on insert, on update, or on a condition you define rather than on a single hardcoded event.
• The action works inside a simple case creation flow and inside a multi stage Playbook, so teams are not locked into one automation pattern.
• It reuses existing template investment. Nothing needs to be rebuilt to move off the Business Rule approach.

🔗 Template Item Dependencies

Task plans used to produce a flat set of tasks that all became actionable at once. Real financial services processes are not flat. For example, evidence should not be requested before a claim is acknowledged. Teams handled this with naming conventions and agent judgment.

A dependency is now a record on the template. You specify a predecessor template item, a successor template item, and a dependency type that controls when the successor becomes available.

Dependency types

• Finish to start: the predecessor task must be completed before the successor can begin. This is the strict gate, and the right choice for compliance sequencing.
• Start after start: the predecessor must have started before the successor can begin. Useful when two workstreams overlap but one has to lead.
• Start together: both tasks become available at the same time, which makes a parallel pairing explicit rather than incidental.

Note: The workspace dependency canvas in the latest release also surfaces a finish to finish pairing. Confirm the full picklist on your instance before publishing this list.

Scheduling intervals

Dependencies also carry a scheduling interval, so a process owner can enforce a mandatory or suggested wait before the successor opens. A required hold between acknowledgment and the next action becomes a configuration on the template rather than scripted logic elsewhere in the platform.

🖥️ Workspace Authoring and Governance

The workspace experience now handles the full authoring lifecycle.

• Visual dependency creation: a canvas view renders template items as nodes with labeled dependency edges, so sequencing is built and reviewed graphically rather than record by record.
• Template items and categories: items, categories, and execution history are separate tabs on the template, with clone, save, and publish actions in the workspace header.
• Configuration records: an admin predefines the item table, view, domain, and hierarchical relationships once, and the process owner selects that configuration instead of hand picking table fields on every template.
• Granular access control: template level ACLs support role based or criteria based ownership, so a template can be scoped to a service organization or a specific line of business.

Example Scenario:

You’ve created a Task Plan Template for a specific FSO case type (e.g., Personal Auto Claim).

This task plan will be invoked when the Stage on a Personal Auto Claim case is ‘FNOL’.

Once the condition has been met, four new tasks will get created for the given case.

🧠 Why This Matters

Automating Task Plan Templates means the system can intelligently generate and apply task plans based on criteria defined at the template level—without requiring agents or admins to manually trigger them. This:

• Reduces manual effort and human error.
• Ensures consistent task execution across similar case types.
• Enables faster response times and better scalability.

💬 Join the Conversation

Have you implemented Task Plan Templates in your organization? What automation strategies have worked best for you? Share your experience or questions below!

[Pascal Pailloc1]

Hello,

Thanks for your post!

We noticed a few issues with the Business Rule. Thanks to Lmouity1, here’s a suggested fix:

(function executeRule(current, previous /*null when async*/) {
     var array = new sn_task_plan.TaskPlanExecutionService().findMatchingTaskPlanTemplate(current);
    var latestRecord = null;
    var latestDate = null;
    for (var i = 0; i < array.length; i++) {
        var currentRecord = array[i];
        var currentDate = new GlideDateTime(currentRecord.sysupdatedon);
        if (latestDate === null || currentDate.getNumericValue() > latestDate.getNumericValue()) {
            latestDate = currentDate;
            latestRecord = currentRecord;
        }
    }
    new sn_task_plan.TaskPlanExecutionService().applyTaskTemplate(latestRecord.sys_id, current);
})(current, previous);

Let us know if it works for you or if you need further clarification

[MattSN]

@Nick Daigneau Is there any official documentation that covers the requirement for this? Anyone installing the plugin would assume that it should automatically generate tasks on a new record whenever task plan conditions are met.

However, based on this post it seems you need to add a custom business rule just for the plugin to function? If this is accurate, this seems like a delivery flaw.

[Nick Daigneau]

@MattSN - As of the Q1 2026 Store release, Task Plan Templates are not automatically triggered when conditions are met — they must be manually invoked from the target record. This post walks through an example of how to trigger them systematically using a Business Rule.

Note that automatic execution is coming in a future release as an enhancement to Task Plan Templates, enabling condition-based triggering through pre-built flow actions — eliminating the need for the Business Rule approach above. I'll update this post when that functionality is available.

[tapiosilver]

is there any documentation on what new sn_task_plan.TaskPlanExecutionService().findMatchingTaskPlanTemplate(current) returns and what other functions are available?

[Nick Daigneau]

For everyone that has commented on this post - the content has been updated based on new enhancements part of the Australia release!