People waste less time, get less confused, and get less frustrated when trying to ensure SPHEREboard has accurate user details like real name and department.
- The user doesn't get clear feedback about if their mapping worked or not
- How do we know when they've given us bad info? (example: First Name: "Jones", Last Name: "Frank")
- Mention how many records were imported/mapped successfully and how many were skipped
- Show a single record (or ten records, whatever) for spot-checking (maybe show a table?)
- We don't inform the user they need to provide HR data or where to do that
- If we know the user hasn't imported HR data yet, show a persistent element that reminds the user they will need to import HR data (and provide a link to it)
- We know the user hasn't imported HR data when the User Specs table is empty (name of table will be changed)
- The "Columns" and "Account Name" fields are very difficult to understand
- Remove these fields for now; we will address this during Ownership Automation... follow up with Rosario about how this works/should work
- Clicking "No column header" resets all progress
- When inputing the file, have the user indicate whether the data has column headers or not
- If mappings have already been set in the UI, translate those to the appopriate column letters
- When we switch to a "Wizard" type flow, persist column mappings when going "Back" or "Forward"
- We have a "full name" and "first name" and "last name" field which seems like it may be a mutually-exclusive situation
- Allow admin to choose format for getting name since we may not know what format this information will be in
- 3 columns (full name, first name, last name)
- 2 columns (first name, last name)
- 1 column (full name as...)
- last, first
- first last
- Entering fields based on columns of the same name is tedious/busywork
- Auto-populate mappings based on common/obvious column names; "First Name" -> "First Name" etc
1.1 The user has no way of knowing where to go to upload their file
1.2 "HR Automation" is a trap, this is not where you upload your file
1.3 "User Account Mappings" is also a trap
1.4 Manually mapping fields seems tedious since field names are identical to column names
1.5 The CSV doesn't have a "Full Name" column, but shouldn't this come from First Name and Last Name? What if it's the other way around and the CSV has a Full Name field but no First Name/Last Name?
1.6 "Account Name" is a very weird field because it's apparently where the user indicates the format of the next field, not where they pick a column (as they've been doing)
1.7 "Columns" makes no sense for a field label; non-sequitur
1.8 Dialog doesn't correctly tell the user if the mapping worked and mentions a path that may not make sense to the end user unless they know exactly how the app works
1.9 Clicking "No column header" resets all fields unexpectedly
1.10 Kristin observed: We don't give the user the opportunity to map hr data to account via employee number
| Seek | Event |
|---|---|
| 25:05 | A4 Prompt |
| 25:53 | Downloads file... |
| 26:18 | Goes to Task Scheduler (Prob 1.1) |
| 26:58 | Goes to HR Automation (Prob 1.1, Prob 1.2) |
| 27:40 | Finds the File Ingestor |
| 28:00 | Gets to the infamous field mapping screen |
| 28:11 | Entering tedious fields (Prob 1.4) |
| 28:17 | There is no "Full Name" field (Prob 1.5) |
| 28:49 | Entering weird fields territory... (Prob 1.6) |
| 29:07 | Entering wrong column (Prob 1.7) |
| 29:19 | Success dialog (Prob 1.8) |
| 29:30 | Confidence question ("4!") (Prob 1.8) |
| 46:28 | "No columns header" (Prob 1.9) |