We have more than 10 reference data tables, that has to be maintained by the users.
Hence, we are planning to delegate those tables. The default OOTB layout for data tables has delete icon for each record for any delegated data type.
But our users doesn't want to view the delete icon as the requirement states do not allow any one to delete the records from the data table.
Do we need to save all the pzRules into the local ruleset and remove the delete icon? Is this the only way?
As this looks a bit tricky - there are lots of rules to save in a local ruleset and sections are invoked dynamically based on the data type delegated.
What are the other possible ways to achieve this?
Have anyone of you had this requirement?
Note: We already suggested the option of removing delete access via Access Role for those data instances and while clicking on the delete icon, user will receive an error. But users are suggesting it is better to hide the delete icon.
I think you need to approach this problem little differently. As you know each action in Pega can be controlled by appropriate privileges or access.
As the UI is not customizable here, you can limit the delete access for the corresponding data class or in other words for the delegated access group only allow read/update access for the data class and then they will not be able to delete a row.
I have used similar approach at my client and has worked successfully.
Another tip which worked for us: Use constraint rules to ensure proper validation error is thrown for any new row, that way you can avoid error entries from users.
If you look back my original question, I have provided the same option as a "Note" and this is what we have suggested to our customer on the first hand. The same approach has been deployed into UAT as well. But our customers are expecting to hide the delete icon.