Standard Ticket Configuration setup non-task extended

[Travis Michigan]

So we have a need on our service portal to see a certain ticket type (Interactions) that are in some cases linked to Incidents.  We have one page now showing all of the interactions that are linked to an Incident, and when people click on it this goes to a default page.  I wanted to configure the information on this page for these Interactions however I didn't see it from the list of tables to select.  Looks like you can only do this with task-extended tables and these Interactions are not.  

Anyone able to point out an alternate way about this, or if I am incorrect about something above?

[Stephanie Leigh]

Hi @Travis Michigan ,

I have a similar need, and I saw an article that suggests to remove the "base_table = task" Attribute for the Table field in the Ticket Configuration table. While it looks straightforward, it might mean tech debt. I'm trying to find other ways other than whipping up a whole new widget, so I wonder how you went about this need?

[Jacques Clement]

We have a similar requirement and did exactly that, that is, removing the task-limiting attributes) on the ticket_configuration table.

This obviously let me select any table of the system and configure it. However when invoking the ticket page from the portal, it does not seem to care about the standard configuration anyway.

I'm stuck here for now; I will report back if I manage to find a way through.