When using display conditions and secured subpages, the list view may incorrectly hide attributes that exist only on subpages that are not to be displayed according to display condition evaluation, even if they should appear due to being on other secured subpages that do not have display conditions and the appropriate view/edit security rights for the subpage are granted.
These attributes still display correctly on property view pages and subpages that have been secured when you navigate to the records. This is not a problem if the attributes exist only on secured subpages that the user has rights to, or if they also appear on at least one other subpage that has a display condition that evaluates true (meaning, the subpage will display when visiting the properties view page).
Steps to Reproduce:
- Create a new master object ('banana')
- Create a new sub page ('dispcondhide') and section
- Add the ID field to the 'dispcondhide' subpage
- Secure the General and 'dispcondhide' subpages
- Add the display condition 1==0 to the dispcondhide subpage
- Publish the views
- Add all global 'banana*' rights to your user
- Navigate to Overview -> banana List
- Click New and create a banana with ID 'testID' and name 'testName' and Submit
Expected: The list view should show values for the testName banana instance record in both the name and ID column.
Actual: The ID column value 'testID' is not displayed and appears blank or unpopulated (actually a hidden and read-only state).
Add an 'always true' display condition on any secured subpages in the view that do not currently have a display condition, so that this part of the test won't result in a final failure.
The display condition '1==1' (which once added will display as '(1 = 1)' by the UI) is sufficient.
Publish the views, and retest. The data shows in the columns correctly now.
Resolved in Clarity 12.1.1
Keywords: CLARITYKB, CLRT-39759, CLRT-47024, clarity12resolved, clarity1211resolved, clarity1206resolved, odf, displayconditions, edit, mode, access, security.