Why is "Requested Item" [sc_req_item] table not extensible?

[williamsun]

I want to create a child table to Requested Item for RFCs to manage them separately and add a whole bunch of other fields that only pertain to Request for Change requests but out-of-the-box it is not extensible.

Is there a particular reason for this?   Can I just make it extensible?   What would be the limitations?

[mitzaka]

William Suncheck the settings of the sc_req_item table. It should have a checkbox for extension.

Have in mind that this table is already an extented table, it's an extension of the Task table. You can verify this here:

http://wiki.servicenow.com/index.php?title=Tables_and_Classes

Still I think you should be able to extend further.

[williamsun]

Great feedback!   I was more looking for a why this was like this.

For example, incident and change_request are already extensions from the task table as well, but these are extensible.

I was thinking that maybe there was a particular reason for this.

[Katie A]

I have the same question. I have several catalog items that require custom fields that ONLY pertain to that particular catalog item. I went ahead and made that table extensible and created an extended sc_req_item table.

However, is this a best practice? Does anyone else do this as a standard practice?

Thank you!