Table structure question

Ace009
Tera Contributor

‎10-04-2023 07:17 AM

Im doing a redesign for an instance that supports several different user bases. The groups each have their own custom table that extends Incident (does not differentiate break/fix vs requests). We're now going to separate and distinguish between ticket types.

The user bases dont really care to work with one another and also have very specific needs as far as data/views are concerned. So I felt it was best to still kind of separate the data and let them have their own tables. The management that oversees all the groups, however, do want reports.

 

I was thinking of having a structure like:

           Task

          Parent Org Table (Extends Task) - contains fields across all user groups like Status/Category/etc

         Group Request/Incident (Extends Parent Org Table) - contains fields unique to each user group

 

What are some technical drawbacks of extending an extended table?

 

 

0 Helpfuls
  • 373 Views
1 REPLY 1

Jakub_Offierski
Tera Contributor

‎10-04-2023 07:30 AM

Some of the drawbacks can be:

  • More complex Business Rules and Scripts of varying kinds (both client and server)
  • If you plan to dot.walk fields in Forms, you should avoid as this is not very good for performance.

Furthermore, proper separation of group should also involve Roles and ACL's to prevent certain things from being seen or executed.

0 Helpfuls