Should I extend the incident table or task table?

[brianmcminn]

Hi All,

I have a customer that has already deployed servicenow and is current using a configured IT Incident application.

I was approached by this customer that they want an identical application, except for Manufacturing Incidents.

Do you think the best approach is to extend the current Incident Table and make a few tweaks to make it manufacturing centric?

Or would it best to extend the Task Table and add all the incident fields and scripts?

I'm most worried that I will harm the current incident process by extending the incident table.

Any guidance is appreciated.

[Pradeep Sharma · Accepted solution]

Hello Brian,

You may find the below blog helpful.

When to Create a New Table vs. When to Extend

[Pradeep Sharma]

Let me know if that answered your question. If so, please mark the appropriate response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list. Thank you

How To Mark Answers Correct From Community Inbox

[adilrathore]

I think extending the incident table would work fine. Plus, if you are extending the task table it may incur platform runtime license as well.

[gtalreja]

First you need to understand the type of relationship it will create between the tables:

If you extend the task table   as you are making an identical application like incident, this way your new table will be sibling of Incident sharing the same parent and can use any fields attributes, and scripts similar to those you need extend from the TASK table,   Then modify the components of your extended table, as needed, to tailor its functionality to the new need.

Extending the Incident Table will make the incident table as parent, but not siblings.

So both the things will serve your purpose, but how you want to use it in future (Reporting, ACLs, etc.. ) will give you your answer.