Different work order task tables

[r2020]

Anyone used different work order task tables based on some fields populated in the work order ? 
it looks like we can use the templates to specify but that is too late if the WOT is already created 

[Ankur Bawiskar]

@r2020 

why would you use other table for work order task when wm_task is tightly coupled with Work order table?

All the OOTB features are available for you to use on wm_task.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[r2020]

We needed to add additional fields to work order task table and we don’t want to add to OOTB table. We will extended the work order task table but we are trying to see how to use that instead of OOTB work order task table. Currently servicenow supports with work type field but we will not be use that if the work order tasks need auto creation and auto dispatch. If I create new work order task table , like routine maintenance and add few fileds, this table is picked up only if I select the work type as something that is configured with this

[Ankur Bawiskar]

@r2020 

you can create custom fields on OOTB table as per customer's requirement.

I will recommend avoid extending wm_task and you will have to check what all capabilities or features are supported on that table and then accordingly do for your custom table.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[AbinC]

Hi @r2020 ,

Using the `wm_task` table for Work Order tasks is indeed the recommended approach in ServiceNow, given its tight coupling with the Work Order table.

Reasons to Use `wm_task`
1. *Tight Integration*: `wm_task` is designed to work seamlessly with Work Orders, offering out-of-the-box features and functionality.
2. *OOTB Features*: Leveraging `wm_task` allows you to utilize ServiceNow's built-in features for task management, reporting, and workflow automation.
3. *Data Consistency*: Using the native `wm_task` table helps maintain data consistency and relationships with Work Orders.
4. *Upgrade and Maintenance*: Sticking with OOTB tables like `wm_task` typically ensures smoother upgrades and less maintenance effort.

When to Consider Alternatives
1. *Specific Requirements*: Only consider alternative tables if you have very specific, unique requirements not met by `wm_task`.
2. *Customization*: If customizing `wm_task` isn't feasible, alternatives might be explored, but with caution.

Generally, for Work Order tasks, utilizing `wm_task` is the best practice in ServiceNow implementations.

If you would this helpful please mark it as a solution 

Thanks,

Abin