Is there a way to make rows in a table and/or a repeating form list in constellation conditionally visible? I don’t see an option for this, which makes me think that I would have to manipulate the underlying page list to remove temporarily invisible rows, but I think that would also mean that I couldn’t just get those rows to reappear as conditions changed without submitting the page and refreshing.
Hi @ChrisBoone
The only way i see to conditionally hide the rows is in the List view where you can apply Filter on columns and that too they should visible in the table columns. No provision for when rules and only custom condition on the columns.
Regards
JC
1 Like
the fact @ChrisBoone says “repeating view” suggests he is using Embedded Data not a List View, so this option would not be available (which makes sense).
@ChrisBoone are you able to confirm are you using Embedded Data, List View or Insights for your “table” of information? And what is the outcome you are trying to achieve?
- Embedded Data - if this is embedded data, a list the user is being asked to capture, I don’t quite understand why rows would be “invisible” as they capture them? This type of capture does allows for some row level conditions, like disabling which might be an option (though still post a usability problem).
In embedded lists, record-level conditions do not provide an option to control the visibility of individual rows. The available controls are limited to enabling or disabling editing and deletion of entries.
During data entry, there is typically no requirement to conditionally hide records in an embedded list, so this limitation is usually acceptable.
However, if you need to display the same repeating view in read-only mode and want certain rows to be conditionally hidden, you can use the following approach:
For a read-only embedded list, you can reference a view defined on the data class that determines how each record is rendered. To implement conditional visibility:
-
Create two views in the data class:
-
Parent View – This is the view referenced in the embedded list configuration.
-
Child View – This view contains the actual fields of the data class that should appear on the UI.
-
-
Include the Child View inside the Parent View.
-
Apply a visibility condition (When rule) on the Child View and define your required logic there.
With this setup, only the records that satisfy the specified condition will be displayed when the embedded list is rendered in read-only mode.
This way you can control the visibility of the records of embedded list in readonly mode.
Hope this helps
Regards
JC
1 Like
@Cheong, Marc
You are correct, I am working with embedded data. I am trying to recreate a form originally built using a section that has rows of data each containing an isvisible indicator. That indicator would be set in response to other actions occurring in the UI outside that record.
@ChrisBoone So here are few more questions from my end,
- Is your embedded list a predefined set of records with certain fields in it shown as readonly or user could take some action on each of the record (for eg. Click on a checkbox or Add text in the field or Select an option from dropdown) ?
- The actions which are occurring outside your embedded list are in the same screen or in a different screen ?
If possible you may want to share a mockup of your embedded list and the other actions as part of your UI for better understanding.
Regards
JC
1 Like
In this case, users are defining a set of questions and criteria for when those questions are displayed (so users can provide data). A response set on question A can then cause question b to go from being IsVisible = false to IsVisible = true.
The key business requirement is that they can define/modify these lists of questions and visibility criteria in production without having to go through a release cycle (like what we would do with pega survey). But you could consider this to be a data driven alternative to PegaSurvey.
Hi @ChrisBoone
Two possible approaches
-
Can we think of building a DX Component of Type layout and define condition visibility?
-
You can use Repeating Layout. In the layout, use a different view where we can possibly define a visibility condition as shown below
Thanks
Kondal
Hi @ChrisBoone
I have spent some time with extending the pyRefreshData DT along with conditionalizing the view and below is the output i have got. Not sure this is what you were looking for. But worth taking inspiration from this and implementing it your way.
Below is my data type which already has few set of questions configured based on certain conditions related to other questions
In the repeating view, whenever user changes the answers, the next set of questions will either be visible or hidden accordingly.
POC implementation
Hope this helps
Regards
JC
1 Like