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.

Sign up for GitHub

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

Jump to bottom

add validation to the form where Visibility values are saved #577

Open
1 task
NicoledeGreef opened this issue Nov 26, 2024 · 0 comments
Open
1 task

add validation to the form where Visibility values are saved #577

NicoledeGreef opened this issue Nov 26, 2024 · 0 comments
Assignees
@danhgov
Labels
Phase 4 - Sprint 4 Nov 26, 2024 - Feb 7, 2025 Priority: medium This issue has a moderate user or business impact and needs to be fixed in next release task a task that a dev team member needs to address

Comments

@NicoledeGreef
Copy link
Collaborator

  • validate Visibility so that a user can only apply Public on its own, or IDIR on its own, or one or more Branch domains (not in combination with Public or IDIR)

That being said, @NicoledeGreef, perhaps we should simply put a form-validation rule, preventing people from putting illegal Visibility combinations in the first place. It could provide a helpful form-validation error message like "A record that is 'public' cannot also have 'Property Taxation Branch' visibility."

Originally posted by @danhgov in #525
@NicoledeGreef NicoledeGreef added Phase 4 - Sprint 4 Nov 26, 2024 - Feb 7, 2025 task a task that a dev team member needs to address labels Nov 26, 2024
@NicoledeGreef NicoledeGreef added the Priority: medium This issue has a moderate user or business impact and needs to be fixed in next release label Dec 16, 2024
@danhgov danhgov moved this from Todo to In Development in MFIN Data Catalogue Feb 8, 2025
danhgov added a commit that referenced this issue Feb 8, 2025
@danhgov
Issue #577: Add constraint on Visibility values.
a212a90
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danhgov danhgov

Labels
Phase 4 - Sprint 4 Nov 26, 2024 - Feb 7, 2025 Priority: medium This issue has a moderate user or business impact and needs to be fixed in next release task a task that a dev team member needs to address
Projects
MFIN Data Catalogue
Status: In Development
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NicoledeGreef @danhgov