-
Notifications
You must be signed in to change notification settings - Fork 447
Open
Labels
Description
This issue is link with some topics :
Description
This improvement will change :
- the featureEditor plugin to automatically use fields params to force feature field value from use's informations
- the featureEditor plugin to allow or not a field to be editable
- the featureEditor to force a field to be not editable if value will take value from user info (this is automatic behavior)
- the fields params on change
This improvement not contains:
- fields UI modification due to UI/UX logic not etablished (according to @tdipisa @offtherailz request)
Use case
Use case 1 : get (autimatic) value from current user's info
(see movie to get more explicit use case example)
- admin open layer's fields params
- admin set fields params to use
user.namevalue ineditorfeature's attribute - next, a user will edit a feature to change a
namefeature attribute - on change,
editorfield have user name value automatically without any action (from fields params)
Here, amenageur field will be autoamtically set from user.name field on each other attribute change :
ms2-issue-valueFromUser-use-case.webm
Use case 2 : set some fields as not editable
(see gif to get more explicit use case and example)
- admin open layer's fields params
- admin set fields params to disabled edition on
nameattribute - next, a user activate edit mode
- He can't change
nameattribute - He can change others attributes
What kind of improvement you want to add?
- Other... Please describe:
Existing feature improvement and changes
Reactions are currently unavailable
