Implications of Extending a Table in a Scoped Application

[shawnclune]

What are the implications -- IF ANY -- of extending a table that is part of a scoped application?

• Does it matter if the "newly created table" is in Global or part of a new scoped application?
• Are there "upstream / downstream" consequences for the "newly created table" that one should be aware of?
• Are there any issues to be aware of with respect to future upgrades?

Thank you everyone for your feedback.

[The SN Nerd]

If you are writing an App with the intention of publishing on the store, you will need to create your own base table.

This is because any changes your make to a table that is not in your app scope will not be packaged with your app.

This means you cannot change an OOB table to make it extensible if it is not extensible OOB.

ServiceNow will not certify your app if you ask the customer to manually make it extensible prior to deployment of your app.

If you are just writing it for a customer, you can do this with the same caution of changing anything OOB, as ctomasi has mentioned.

[ggg]

My scenario is:

I am creating a scoped app using Test Management which is global.

I extended all of the tables in Test management in my scope because i want to add fields / script and not update the global table.

At the same time, i want to keep all of the OOB Test functionality.

I therefore need the oob field names for the parent / child relationships.

I also need my custom tables in related lists because I want to click NEW and have my custom form display.

does anyone have experience with this?

I am hitting some stumbling blocks where the OOB functionality breaks.