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

UI improvement: select form step design & renaming #1029

Closed
spwoodcock opened this issue Dec 6, 2023 · 7 comments · Fixed by #1366
Closed

UI improvement: select form step design & renaming #1029

spwoodcock opened this issue Dec 6, 2023 · 7 comments · Fixed by #1366
Assignees
Labels
enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority

Comments

@spwoodcock
Copy link
Member

  • I think it was mentioned a while ago that 'Form' is quite an opaque term for users.
  • A much more user friendly term would be 'Category'.
  • Form should be renamed Category in the user facing UI in the following:
    • The url /select-form --> /select-category
    • The stepper and card title: Select Category
    • Text Select form category --> Select category

Then I feel the UX for the following can be improved:

image

  • Remove the radio. I think the default should just be the user selects a category, unless an advanced user wants to upload a form.
  • There should be a checkbox that says: Upload a custom XLSForm instead.
  • When the user checks this, the file uploader appears.

What do you think @susmina94

@spwoodcock spwoodcock added the enhancement New feature or request label Dec 6, 2023
@spwoodcock spwoodcock added priority:high Should be addressed as a priority frontend Related to frontend code labels Dec 7, 2023
@manjitapandey
Copy link
Contributor

Is something like this works fine?

image

@spwoodcock
Copy link
Member Author

Looks good!

I like that the file picker is hidden and can be expanded out.

In this case, I don't think there is need for the checkbox. If the user selects a file, then we use the custom extract.

@spwoodcock
Copy link
Member Author

spwoodcock commented Feb 1, 2024

I update the text and routes from form --> category in PR #1123
The UX changes are still required though 👍

image

@spwoodcock
Copy link
Member Author

spwoodcock commented Mar 2, 2024

This is mostly done, the only thing to update from the original requirement is to use a checkbox instead of radio for selecting a custom form.

  • If the user checks the box to upload a custom form, then the uploader appears.

Category selection on custom form:

  • The category selection should be mandatory, even if the user uploads a custom form.
  • However, they may have a category type that we don't cover in our predefined types.
  • Should we also provide an option for the user to type in their custom category name?

@manjitapandey
Copy link
Contributor

If we allow users to add custom category name, and upload custom form, They need to add Yaml file too. Are we planning to add that section?
Also pinging @nrjadkry through the conversation.

@spwoodcock
Copy link
Member Author

spwoodcock commented Mar 4, 2024

Good point - we would need to enforce uploading a custom data extract.

Allowing custom input overcomplicates things for now - let's consider as an option in the future if there is demand for it. The database supports it if we need.

@manjitapandey
Copy link
Contributor

@spwoodcock are you going to do the UI changes? If you haven't we can assign it to @NSUWAL123 for UI fix?
Providing option to add new category may need some more discussion and research.

@spwoodcock spwoodcock moved this from Deployed to Done in Field Mapping Tasking Manager (FMTM) Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority
Projects
Development

Successfully merging a pull request may close this issue.

4 participants