how to choose the right tables to extend

[Blair Dee]

I am new to serviceNow development and trying to get a handle on best practices when creating a new app.  I created a personal developer instance and I would like to create a sample app called Remote Work.  The concept is that it would be an app where employees would fill out a form requesting to work remotely.  Once the request is submitted it would need to be approved by a manager and then by HR before it is marked as approved.

this is a fictional app, but just something I am using as an example.

my thought is that maybe when I create this app I could extend the incidents table instead of creating a new table from scratch for the requests.

If I want to extend a table, how would I know if incidents is the best fit?  Is this just something that comes with experience, or is there a master list somewhere that describes the properties of existing tables and apps so I can have a better idea of which I might want to extend when creating a new app?

[Nia McCash]

The Task [task] table is typically the table that's extended (not Incidents). This tutorial may help you get started: https://developer.servicenow.com/dev.do#!/learn/tutorials/rome/parent_tutorial_departmental_request_...

There is also a whole Application Development Fundamentals course available from ServiceNow, but that one has costs associated.

You might also want to consider participating in the #BuildWithAES challenge with your app if you'd like.

[Yousaf]

HI Blair,

There is not a straight answer but this could help you.

when to Create a New Table vs. When to Extend

Mark Correct or Helpful if it helps.