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

Min/Max only has date view, not working for number fields #420

Open
mikemitchel opened this issue Jan 29, 2025 · 1 comment
Open

Min/Max only has date view, not working for number fields #420

mikemitchel opened this issue Jan 29, 2025 · 1 comment

Comments

@mikemitchel
Copy link
Contributor

The min and max value fields are expecting date-formatted values, rather than numbers. As we don't tend to use these for Number and Number (Dollar), this shouldn't be an issue as long as these fields remain blank. However, since "Number (Pick from list)" type fields require the min and max values to be defined for the list to be filled out, these questions are not working at the moment. All you see is a blank dropdown list, with no option to select anything.

Having poked around a bit, it looks like this issue carries over to the environment that we test our pathways on, but it only affects questions that you've opened in A2J Author since this issue began. So, if you were to publish a pathway without opening any of the specific questions that contain a Number (Pick from list) field, it should be fine, but if you have opened one of these questions, you're likely to run into a question that you can't move past, since many of these fields are set as Required, and you're unable to select anything from the list.

Image

@mikemitchel mikemitchel changed the title Variable search gives false positives Min/Max only has date view, not working for number fields Jan 29, 2025
@mikemitchel mikemitchel moved this from Todo to In Progress in CLEO Bugfix/feature project 2024 Jan 29, 2025
@mikemitchel
Copy link
Contributor Author

The companion fix to this involves the Viewer, which currently only shows the expected 'range' of answer if you get it wrong. I have a fix, using the current styling which might be 'good enough' always showing the current expected ranges, but it would better to have a translation for this in other languages. Perhaps we could fix it when we fix the date format enhancement, and do a larger localization overhaul for translations, numbers, and expected dates and currency.

Image

NOTE: number list doesn't need the range, as the selector already enforces it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant