---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Task plan template

# Task plan templates driven order fulfillment {#ariaid-title1}

Release version: Brazil  
Updated September 27, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Task plan templates driven order fulfillment

Task plan templates in ServiceNow provide a no-code method to define and orchestrate the fulfillment journey for products by standardizing tasks and their dependencies across product orders.
This feature offers an alternative to Flow Designer, enabling more flexible product configuration workflows without developer involvement.
When a domain order is created, the system automatically applies a matching task plan template based on the order's specification and action, generating the necessary order tasks.
This task orchestration capability is available in Sales and Order Management deployments regardless of the presence of Sales Customer Relationship Management for Telecommunications (SOMT).
Show full answer Show less  
**Note:** Automatic closure of domain orders is not active by default and requires custom implementation.

## Key Features

* **No-code task orchestration:** Enables non-technical users to define fulfillment journeys and manage task dependencies.
* **Task plan templates:** Act as containers grouping template items (tasks, child cases, or child case tasks) that represent the tasks to be created and orchestrated.
* **Template item conditions:** Allow setting criteria to determine when specific template items apply, enabling dynamic and conditional task creation.
* **Task dependencies:** Define predecessor and successor relationships among tasks to ensure correct sequencing and reduce ambiguity during fulfillment.
* **Publishing workflow:** Templates can be edited while in Draft state and published to activate their application on domain orders, provided no conflicting templates exist.

## Practical Use and Benefits

* **Standardize and accelerate fulfillment:** By using templates, organizations can ensure consistent task orchestration across different products and orders.
* **Reduce IT dependency:** Business users can create and modify fulfillment processes without needing developer support.
* **Manage complex task sequences easily:** Task dependencies help agents understand when tasks should start and finish, improving operational clarity.
* **Flexible configuration:** Conditions on templates and template items allow tailoring task creation to specific order scenarios.

## How to Create and Configure Task Plan Templates

* **Create the task plan template:** Define the overall container and specify conditions for when it applies to domain orders.
* **Create template items:** Add tasks or related records that represent the steps in the fulfillment journey, supporting hierarchical relationships.
* **Set conditions on template items:** Specify when individual tasks should be created based on order criteria.
* **Define task dependencies:** Establish predecessor-successor links to control task sequencing.
* **Publish the template:** After finalizing the template and its items, publish it to enable automatic application on matching domain orders.  
Use the task plan template to define tasks and their dependencies that are needed to orchestrate the fulfillment journey for a product to standardize fulfillment processes across products.
A no-code approach in ServiceNow® that allows you to create task orchestration workflows using task plan templates. It as an alternative to flow designer, giving more options for implementing product configurations.

For more information about Flow actions for fulfillment subflow definition, see [Flow actions for fulfillment subflow definition](https://servicenow-prod.fluidtopics.net/fgZ5huXuUingI64l2hkLmg "If you define your own fulfillment subflows in Workflow Studio, you can use the standard flow actions that are available in the ServiceNow AI Platform. Each action deals with different aspects of the fulfillment or inventory maintenance that provides some consistency in retrieving and updating data.").

When the template is configured for a specification, the domain order creation automatically searches for a matching template, based on the task's specification and action of domain order. When a template match is found, the
template is applied to generate the order tasks under the domain order. To learn more about task plan template, see [Task plan templates](https://www.servicenow.com/docs/access?context=task-plan-templates&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US).  
Note:  
This task orchestration integration for domain orders is available in Sales and Order Management deployments, whether or not Sales Customer Relationship Management for Telecommunications (SOMT) is installed.  
Important:  
Automatic closure of domain orders is currently inactive and will require a custom implementation.

## Benefits of task plan template {#somt-flow-action-catalog-task__section_osf_lzg_j3c}

It enables non-technical users to do the following:

* Define fulfillment journeys.
* Manage task dependencies for simple task creation without developer involvement.
* Reduce IT dependency.
* Accelerate deployment of new offerings.
{#somt-flow-action-catalog-task__ul_cqs_4zg_j3c}

## Create a task plan template {#somt-flow-action-catalog-task__section_qdv_pp2_k3c}

You can create a task plan template by following these steps.
{#somt-flow-action-catalog-task__table_xq4_wp2_k3c__entry__2}

| Step | Explanation |
|-|-|
| [Create a task plan template](https://www.servicenow.com/docs/access?context=create-task-plan-template&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US). | Create the template and set the conditions as to when the template applies. * The template functions as a container or group of template items. * The template identifies a plan to apply the associated template items. {#somt-flow-action-catalog-task__ul_uzm_clx_qfc} |
| [Configure task plan template](https://www.servicenow.com/docs/access?context=configure-task-plan-template&version=brazil&pubname=brazil-telecom-media-technology&ft:locale=en-US) | To add conditions to a template item that determines when a template item is applicable. |
| [Create one or more template items](https://www.servicenow.com/docs/access?context=create-task-plan-template-item&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US). | Create the template items to include in the task plan template. These items can be tasks, child cases, or child case tasks. * Template items are the tasks or records that are to be created when the template is applied. * Template items can be used to define a hierarchy of parent and child entities of any task type. {#somt-flow-action-catalog-task__ul_hxg_hlx_qfc} |
| [Create conditions for template items](https://www.servicenow.com/docs/access?context=create-task-plan-template-item-condition&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US). | Set conditions as needed for each of the template items that identifies when a template item should be created. |
| [Task dependencies for task plan templates](https://www.servicenow.com/docs/access?context=task-dependencies-for-task-plan-templates&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US) | It provides controlled sequencing within the generated records from the template items in the Task Plan Template Dependency table. By defining predecessor and successor relationships, the tasks can start at correct time reducing ambiguity for agents. |
| Publish the task plan template. | While in the Draft state, you can make changes to the template, template items, and template item conditions. It allows to publish if the same condition template is not available. Publish the task plan template to apply it to cases and case types. To publish a task plan template, select Publish on the Task Plan Template form. |
[ ]

{#somt-flow-action-catalog-task__table_xq4_wp2_k3c}
* **[Configure the task plan template](https://servicenow-prod.fluidtopics.net/0Fxqs5kkR2WlBWlbS7nrzw)**   
  Configure the task plan template to add conditions to a template item that determines when a template item is applicable for domain orders.

