Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • Enhancement suggestion: DataSourceField canUpdate analog to canSave

    Hi Isomorphic,

    I think I found another useful feature for your framework. In some cases there are fields that may never be updated after being added (canSave="false" does not work here), for example: startSalary, startDate, ...
    Here a new canUpdate="false" might help.

    This then should only strip out values in update-requests on the server side (like its currently done for canSave="false").
    Additionally it would be good if in DynamicForms the canEdit of that fields is adjusted to the DynamicForm-mode (add or update), so this .ds.xml-attribute must be transmitted with the DataSourceLoader result.
    Same for ListGrids, startEditingNew() allows editing, normal doubleclick-editing does not.

    Best regards
    Blama

  • #2
    We do have this distinction already via initRequiresRole and editRequiresRole. So one way to get what you describe would be to set editRequiresRole to a superuser role only used for admins.

    Comment


    • #3
      Hi Isomorphic,

      thanks for the hint on this one. I think an editRequiresRole="false" where false is a non-existing role should then solve this. I'll give it a try.

      Best regards
      Blama

      Comment

      Working...
      X