Add Option for Non-Editable Fields in Record Portlets
Currently, the biggest issue with record portlets is that any field displayed on the portlet becomes editable. While one can ignore the fields they don't want to be editable in the update statement, there is no built-in option to explicitly make a field not editable in portal 2. This causes confusion among users as to why certain fields are not updating. Therefore, we request the addition of an option for non-editable fields in record portlets. This feature will improve user experience and allow administrators to define specific fields as read-only, enhancing data integrity and user clarity.
AdminJeffery Maynard
(Product Support Consultant, Novacura)
shared this idea
We are pleased to announce that the requested feature has been fully developed and is now available to all users. Our product team has tested the feature and ensured that it meets the requirements and specifications. We hope you enjoy using it.
Released in version 2023.3.