Closed beparticular closed 2 years ago
@jeromeleecms can you share the approval letter and information about what cannot be changed here? thx!
@beparticular
Looked at this on Friday and conferred with Jerome and Laura. The solution that Laura and I found out at the end of the day is I think the most promising.
This instance could either initiate when an overflow of integers is high enough or be a state that always occurs.
The alternative is a scrollable version that initiates when the integers are too long.
Per separate conversations with Jerome and Jesse, this table is there to help verify your acceptance letter information and matches to a table in the acceptance letter. If it doesn't match, it is an indication that something is wrong that needs to be traced back to the budget summary table.
If this is a a point of connection between the acceptance letter and data entered by the user, it would be great if we could make this work without breaking it up, and without the scroll. Currently there are no scrolling issues in the export view, only the builder.
Let's hold this to look at while moving forward on the update experience. The question I think is - will folks be looking at the export view or the builder to compare this to the acceptance letter, and what will that look like, or what will folks be instructed to do in the future based on our research.
Per discussion, this isn't a priority issue right now and we will fold this into the update experience research.
Closing this in favor of when we do the MDBT content/functionality with MMIS.
With the implementation of the non-rounded numbers across the app, there are just a handful of places in the app where this may cause a readability issue for tables and numbers. This screenshot is the MMIS table on the Executive Summary.
Let's explore of a new way to show the data in this table that is readable for large numbers, doesn't break the page, and meets any regulations with the approval letter.
This task is done when...