Service Operations Workspace - Related Records controls configuration

Mattsharples
Tera Contributor

5 hours ago - last edited 5 hours ago

Hi all,

 

I'm currently trying to understand where (if anywhere) the new style of related record list view can be configured, it mirrors what is now shown on list view within Service Operations Workspace however unlike standard lists which can be configured via the sys_ux_list record to include things like the new quick edit functionality but also disable links, I can't find any such table or record that controls the logic behind the related list functionality.  

Mattsharples_0-1769093738649.png

While the related list itself does pull from the normal relationships & list layout to decide what it should / shouldn't show. It completely ignores the list control functionality so hiding things like ability to stop filtering, order by e.t.c aren't possible. I've also small features like dependant fields updating live when you edit from list view no longer work but this is secondary at the moment.

I have been able to go back to the old style by excluding certain tables from the Variant that is using this list style (SRP Record from "Record Page for Service Operations Workspace" plugin) but I'm hoping there's a way to take advantage of this newer style without losing out on configuration options

 

0 Helpfuls
  • 66 Views
1 REPLY 1

Matthew_13
Mega Sage

an hour ago

Hi Buddy,

The newer related list used on SOW reccord pages is not driven by sys_ux_list and does not have an equivalent table or record where list control behavior can be managed. Its rendered by a dedicated workspace component, which means it intentionally ignores classic List control settings such as disabling filters, ordering, or other interactive list controls. Thats why features you’d normally expect from standard lists like fine-grained control over UI actions or some live dependent-field behavior dont apply here.

What does still apply that I see is the underlying relationship definition and list layout/view which is why columns and basic filtering behave as expected. Beyond that, the configuration surface is currently limited.

At the moment, the practical options are:

  • Continue using the legacy related list where you need full List Control behavior as you’ve already done via the variant exclusion or..

  • Use a workspace list component filtered by the parent record if you need the newer list capabilities that are governed by sys_ux_list, or

  • Go fully custom with a UX component if you need both the new look and strict control over available actions.

Basically, there isnt a supported way today that I know of to fully configure the new related list the same way you can a standard list. The tradeoff with the newer style is a reduced configuration surface in exchange for a more opinionated, workspace-optimized experience.

 

@Mattsharples - Please mark Accepted Solution and Thumbs Up if you found helpful

0 Helpfuls