Wireframe out improved UX to IT standards modal

[hatfieldjm4]

Currently the IT standards modal is the description field and then a large table. We need a way to better display this information with the most pertinent data fields first. The user should be able to see most of this data without scrolling.

[hatfieldjm4]

@joshsjurik Here are my notes on the requests from the IT Standards team (Andrew and Cindy):

• [x] Logic to only show the data field, “Approved versions”, if the status is approved. If the status is anything else, this data field won’t appear.
• [x] - Andrew requested a hover over the color to denote what it means (for the stoplight on the status, approval expiration date, and 508 compliance)
• [x] - If FedRAMP data field is N/A or null, it shouldn’t show up
• [x] - The flow of data fields should be: Status --> included versions --> expiration date --> software release name --> also known as --> 508 --> POC
• [x] - Change "End of Life Date" to “Vendor End of Life Date”
• [x] - Change "Approval Expiration Date" data field name to “Approval Expires”
• [x] - Center justify the date under the Approval Expiration Date data field

[joshsjurik]

• [x] Show all fields button
• [x] Make sure icon colors are accessible
• [x] Bring more attention to the top section

[hatfieldjm4]

• [x] Please make the table view for the "non-critical" data the standard view. We probably don't need the other view.

[joshsjurik]

@hatfieldjm4

I removed all of the wireframe tabs and moved the selected wireframe into the main overview tab.

I also removed the list view for the non-critical data and added the attribute definition tooltips to the rest of the headings.

The next steps are to update the "approved versions" field once we get the db up to date and also add in the definition to the data dictionary table for it so we can pull that tooltip data the same way as the rest.

[hatfieldjm4]

@joshsjurik

Thanks, Josh. I created a column, "approvedVersions" in the dev database and populated it based on what we currently have in the "Keyname" field now. Here is the SQL script to create the table, which we'll use in prod.

ALTER TABLE `gear_schema`.`obj_technology` ADD COLUMN `approvedVersions` VARCHAR(45) NULL DEFAULT NULL AFTER `RITM`;

[joshsjurik]

@hatfieldjm4

I updated the front end to use this new db field. I also added the term and definition for "Approved Versions" to the data_dictionary table and updated the "Approved Versions" tooltips to pull from there instead of being hard coded.

I also added the "Approved Versions" field to the IT Standards report and updated the "Approval Expiration Date" and "End of Life Date" fields to match what we changed them to in the modal view.

One question I do have is what should we show if the "Status" is "Approved" but the "Approved Versions" is empty? Right now it's just blank but I wasn't sure if having it blank would cause more confusion for users. Once we discuss this I can make any changes we decide on and create a PR for this.

[hatfieldjm4]

Good question. Before launch, ideally we'll fill in >90% of the data for the approved versions field so that it will be rare that the data field is empty. The data import I've done for the approvedVersions field accounts for about 76% of the approved titles. I'll work to increase that number even further prior to launch.

[hatfieldjm4]

@joshsjurik Unless I'm mistaken, we do still have to add the "Approved Versions" field to GEAR Manager so that the IT standards team can maintain the data. If this hasn't already been done, would you please add an issue for it?