Hello,
I try to apply writabilitygates on a table (collection) but without success. I tried to put the writabilitygate once on the model and once the table-view, both without succes. In both cases, the behaviour I get contains an error:
I can create and edit rows in the table, but when I log out and again in as the same user, without having changed the table or surrounding entity, I ca no longer edit.
My question first is how to put writability constraints on tables. Perhaps there is another way that what I am doing.
For reasons of completeness I already attach the model and view where I encountered the strange behavior: The model contains the entity "Deal" that contains the table "attachment_table". The scenario to reproduce the problem is as follows: Log in as SalesExecutive, create a deal, enter a name, open the deal and make a row attachment, choose “submit” as value for the status field and save. Now you can still edit the row. Log out and log in again: now you can no longer edit the row.
Perhaps this question is related to bug-issue 3041251 where I ask explanation on writabilitygates on components.
Thanks,
Marc
| Attachment | Size |
|---|---|
| model.xml | 12.46 KB |
| view.xml | 10.4 KB |
| frontend.xml | 13.04 KB |
