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

CTHUB - Implementation of File Requirements #402

Open
4 tasks
Lalita-Lala opened this issue Oct 22, 2024 · 1 comment
Open
4 tasks

CTHUB - Implementation of File Requirements #402

Lalita-Lala opened this issue Oct 22, 2024 · 1 comment
Assignees
Labels
Low Low priority Task Any work that does not directly impact the user Tested :) Passed testing

Comments

@Lalita-Lala
Copy link
Collaborator

Describe the task
Implement a file requirements feature that will be visible to users after a program has been selected. This feature will provide users with specific guidelines on how to prepare their dataset to meet system expectations, ensuring proper formatting and structure before file upload.

Mockups
Prototype - https://www.figma.com/proto/K7gNHRnlYuG27w8XGVquY5/Warnings%2FErrors?page-id=0%3A1&node-id=563-275&node-type=frame&viewport=1489%2C-616%2C0.09&t=dyOi09ahQ34TwtGe-1&scaling=scale-down-width&content-scaling=fixed&starting-point-node-id=563%3A275
Mockups - https://www.figma.com/design/K7gNHRnlYuG27w8XGVquY5/Warnings%2FErrors?node-id=567-799&t=D1b6xL7cuq7xDBsp-1

Purpose
To guide users in preparing their datasets according to the necessary criteria, avoiding errors and ensuring a smoother upload process. The file requirements will offer detailed instructions about the sheet name, required columns, and file format, which users must follow.

  1. Sheet Name:
    • The sheet name must be included in the dataset and will correspond to the selected program.
    • For instance, if the user selects Go Electric Rebates Program, the sheet name will reflect that program “Distribution List - Master”. If the program changes, the sheet name will automatically update to the new program’s requirement.
  2. Column Names:
    • All required column names must exactly match those provided in the template. This ensures consistency and proper alignment with the system’s expectations.
  3. File Format:
    • The required file format will be clearly specified, ensuring users understand the acceptable formats (e.g., .xlsx).
  4. Persistent Visibility:
    • The file requirements will remain visible on every subsequent screen after the program is selected, ensuring that users have continuous access to the necessary information as they navigate through the flow.
    • This section will not disappear or change position, providing ongoing guidance throughout the process.

Acceptance Criteria

  • The file requirements must become visible after the user selects a program.
  • It must include specific details about the sheet name, required columns, and the file format.
  • The sheet name provided in the file requirements must dynamically update based on the program the user selects. For example, if the user selects Go Electric Rebates Program the sheet name must correspond to that program, and it will automatically update if a different program is selected.
  • The file requirements section should remain visible on all subsequent screens after the program is selected.
@ArawuSamuel1 ArawuSamuel1 added Low Low priority Task Any work that does not directly impact the user labels Oct 30, 2024
@tim738745 tim738745 self-assigned this Nov 4, 2024
@katerinkus
Copy link
Collaborator

katerinkus commented Nov 26, 2024

Hi @shayjeff and @tim738745,
I can see them now, they look good to me! Thank you Tim 🙂

@shayjeff shayjeff added the Tested :) Passed testing label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Low Low priority Task Any work that does not directly impact the user Tested :) Passed testing
Projects
None yet
Development

No branches or pull requests

5 participants