Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fields - Editable field and allow to calculate field from user infos #10523

Open
1 task done
Gaetanbrl opened this issue Aug 30, 2024 · 0 comments · May be fixed by #10524
Open
1 task done

Fields - Editable field and allow to calculate field from user infos #10523

Gaetanbrl opened this issue Aug 30, 2024 · 0 comments · May be fixed by #10524
Assignees
Milestone

Comments

@Gaetanbrl
Copy link
Contributor

Gaetanbrl commented Aug 30, 2024

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

⚠️ WARN : Next captures shows some new field's form control temporary developped to test full chain from fields params to attribute table field.

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.name value in editor feature's attribute
  • next, a user will edit a feature to change a name feature attribute
  • on change, editor field 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 name attribute
  • next, a user activate edit mode
  • He can't change name attribute
  • He can change others attributes

ms2-issue-editableField-use-case

What kind of improvement you want to add?

  • Other... Please describe:
    Existing feature improvement and changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants