Anonymous
My feedback
6 results found
-
7 votesAnonymous
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Anonymous
commented
dasd
-
3 votes
-
1 vote
-
28 votesAnonymous
supported this idea
·
-
6 votes
An error occurred while saving the comment Anonymous
commented
I second this idea. I realize this is a training issue, but it keeps coming u
The UI aspect of this page is confusing to users: the three sections can be collapsed/expanded by users, and Aeries remembers the last state (expanded vs collapsed). Users who seldom use the page forget to expand the sections then think there is no PGM entries for that student.
Today's example, a user added a new entry for PGM page, but the section for "Current Programs" is collapsed by default. User did not see their new entry, and they think that "save failed", so they add it again. Rinse and repeat many times, until they call IT in frustration.
One potential solution is to add the number of entries ("counter" from Dana's idea) for each section in parenthesis, if the section is collapsed. For example:
Special Programs (6)
Program Screenings (2)
Program History (16)Thanks!
-
152 votesAnonymous
supported this idea
·
This is an old Idea, but I had just submitted a related ticket as well, so tacking on.
If custom tables were surfaced via API, it would be ideal if Read/Update/Insert were options as well.
we have partner resource that read data from API, then we have to extract and write to Aeries via scripts, etc.
It would be more secure and streamlined to surface tables via API.