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 

[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

[Dr Atul G- LNG]

Hi @r2020 

I don’t think it’s a good idea to create a table similar to wm_order. You can use a view instead to display limited fields based on your role.