Extending Request, RITM and SC Task table.

[Community Alums]

Hi All,

We have  ITSM already implemented. Now we are building a custom app related to HR module in same instance in Global scope. We have created our separate portal for HR. Now we are creating service catalog also for HR related activities. But our REQ, RITM and SC Task tables are customized in our ITSM implementation, mainly the state field in these 3 tables. So we are planning to extend all these 3 tables and customize them according to our HR related requirements, for HR we want to have different states for all these 3 tables(like work in progress, on hold, cancelled etc).

So my first question: IS it possible to extend all these tables?

2nd: What issues we will be facing if we extend these tables while implementing for HR service catalog?

3rd: Will our workflows, Approvals and other items like create sc task (in workflow) will work properly for our extended tables also?

OR, we should not extend these tables and use the same ootb tables (REQ,RITM,SC Task) and customize them using ui policies and client scripts.

Thanks in advance.

[Uncle Rob]

I only extend tables if its a definitive similar type of task that has its own ...
- unique field properties
- Security constraints.

If you're thinking about extending the table as a remediation for a mistake you already made on what would have been a perfect table, you're throwing gasoline on a dumpster fire.

"We did this unwise thing so we should do this other unwise thing to compensate / avoid the consequence" is just compiling the headache a future you will deal with.

[jamesjimi]

Extending the Request, RITM (Request Item), and SC (Service Catalog) Task tables in compliance with the law involves implementing measures to ensure data privacy, security, and accessibility. This may include defining data retention policies, setting up access controls, conducting regular audits, and complying with relevant regulations such as GDPR, HIPAA, or CCPA.