The last relevant community post I could find on this topic was from 2015. And the consensus then was clearly "strongly advise against." I want to bring it up again to see if anything's changed. I'm not so ambitious that I want to extend the whole Catalog/Catalog Item/Request/Request Item ecosystem.
But I am strongly considering extending the Catalog Task table (sc_task) to a new scoped app. In my mind, this allows the segregation of labor required to fulfill, (and the reporting on labor) but maintains the native #itsm cart features and the catalog item (and RITM) can be maintained & accessed from the global scope. I'm aware that I'll have to configure cross-scope access.
The Catalog Task table is not wildly different from the general Task table, yet is not extensible out-of-the-box.
Why shouldn't I extend the sc_task table? What am I overlooking or forgetting?
