Hiding Record Screen Segment if there that screen is empty

Thomas Geesman
Tera Contributor

Is there any way make screen segments hidden in Mobile? I have added a screen segment to a task record for a checklist. If there is no checklist tied to this record, I would like to hide that screen segment completely. Is there any way to achieve this? 

6 REPLIES 6

Tim Preston
Tera Contributor

Just wondering, did you ever figure this out? Was just trying to figure out how to do the same thing. The only thing I could think of was adding a list item config that took the user to a different record screen that didn't have the record screen segment if the conditions were met, so I was wondering if you found a better solution.

 

Thanks!

In case anyone is interested, it’s not an ideal solution, but my above idea seemed to work for us. If you are accessing the record screen from a list, you can add multiple list item configs to your list and give those list item configs conditions, so if you are looking at a list of records from the task table (incidents, catalog tasks, etc.) you can have completely different cards and record screens depending on what conditions you have set. I haven’t tested it, but you could probably have some cards execute a function instead of taking the user to a record screen while other cards take a user to a record screen since that is defined in the list item config.

 

Basically, what you want to do is create the following:

  1. List Screen
  2. Item Stream Segment
  3. List Stream
  4. Data item for the above list stream

After you create the above records:

  1. On the list stream create or select a list item config with all the details you want
  2. Repeat the process by creating/selecting a second list item config on the list stream with a different record screen

TimPreston_0-1732655943706.png

 

  1. After you create both, add the order and specify the conditions for when to use each list item config on each list item config record

TimPreston_1-1732655943709.png

 

Like I said, it’s not an ideal solution for several reasons. For instance, you must create 2 different list item config records with 2 different record screens. But, it seemed to work for us though.