Currently, our Post-Acceptance grid 'Complete View' is not organized well at all. Unlike the General Application grid view, where the data displays in a logical format, regardless of what the Form Field ID is (i.e. Imported Applicant Information, Application Questions, Imported Administrator Information – in that order), the Post-Acceptance grid displays a seemingly random order of Import Data and Post-Acceptance questions. As aforementioned, this is apparently due to when the item was created and the Form Field ID it was given upon creation. While this may make sense to BAM on the back-end, it makes no practical sense for users. I think updating the default view would go a long way towards improving usability and user experience. Given that the system is able to accommodate this in some large grids, I suspect it could do the same with the bulk action grids.
While I've submitted enhancements regarding only being able to see post-acceptance questions from your scope in this grid previously, this is a different issue as this could affect anyone, depending on the Form Field ID that BAM generates.
Finally, while the Support Team continued to push Saved Grid Views as a potential fix, this seems like a band-aid solution. Instead of users across the country spending time saving their own grid views (that would need to be maintained as new questions and new Import Data fields are added to the system), I'd like to see some development on the BAM end instead that addresses the root of the issue.
Client Name "shard name" | wisc |
User | System Admin |
Functional Unit | Post Acceptance |
Employee Name | Keith Brown |
This issue continues to come up for this where users see ALL of the post-acceptance questions in the system in the PA bulk action grid, not just those that they're scoped to (and care about). While you can save grid views for them, it requires maintenance and/or searching through hundreds of questions when you add a new question and need to add it to grid views.
Making the bulk action grids more user-specific would go a long way towards improving our user experience at UW Madison
We also ran into this with Disbursement Fields in Stewardship Management - though a user would only need to work with their scope's post-acceptance questions (given that a) the opportunities they have access to have those questions only and b) that their awardees would only have answered those questions), users see all the post-acceptance questions as an option for 'Contact Visible' (example: https://wisc.academicworks.com/donor/admin/funds/3837/disbursement_fields). This is confusing and an unnecessarily large list for users to have to go through - this should be scope-limited, just like the post-acceptance question library is where they would set something to 'Stewardship Visible' in the first place.
UW-Madison is still interested in this functionality.