Chris Holloway
My feedback
95 results found
-
2 votesChris Holloway
shared this idea
·
-
2 votes
-
1 voteChris Holloway
shared this idea
·
-
1 vote
An error occurred while saving the comment Chris Holloway
shared this idea
·
-
35 votes
-
1 voteChris Holloway
shared this idea
·
-
11 votes
An error occurred while saving the comment Chris Holloway
commented
The new error page, which does not display error information to the user isn't helpful for common issues like missing a required field (like a date -- which can't be defaulted either)
Chris Holloway
supported this idea
·
-
2 votesChris Holloway
shared this idea
·
-
22 votes
An error occurred while saving the comment Chris Holloway
commented
Common areas as well:
"Search students, pages, classes"
User options sub-menu
"Change Password"
"Change Email"
"Add New Student to Your Account"
"Log out"Chris Holloway
supported this idea
·
-
2 votesChris Holloway
shared this idea
·
-
18 votesChris Holloway
supported this idea
·
-
4 votes
An error occurred while saving the comment Chris Holloway
commented
This issue has occurred again for me this year. I extracted the ORA files and at the same time another staff member extracted the SENR for CALPADS. This caused multiple of our schools to be missed during the CALPADS extract.
Please implement a fix for this!
Chris Holloway
shared this idea
·
-
4 votesChris Holloway
shared this idea
·
An error occurred while saving the comment Chris Holloway
commented
I have struggled for years with the issue of having the correct No Show date be used - because the No Show Wizard does NOT help our users make the correct choice.
I have submitted two tickets previously, and then frankly gave up - as it was clear that a solution to my problem (which everyone MUST be experiencing as well...) just wasn't going to happen.
https://support.aeries.com/support/tickets/archived/165275
https://support.aeries.com/support/tickets/archived/232712The support response was always - this is USER ERROR --- refer to the No Show Guidelines.
https://support.aeries.com/support/solutions/articles/14000050200-no-show-guidelinesWell, I just can't accept that Aeries can not be modified to function better and solve a VERY COMMON issue.
So, Here is my solution proposal.
Modify the No Show Setup:
https://support.aeries.com/support/solutions/articles/14000070848-no-show-setupHave two configurable No Show dates
- Prior Year Exit Date
- Current Year Exit DateThen the No Show Dialog that appears when selecting the No Show Code on the Demographics page, can evaluate the STU.ED and choose the correct default:
If STU.ED is within the current school year - use the configured "Current Year Exit Date" from the No Show Setup.
If STU.ED is before the first day in the current school year (meaning the student was enrolled in the previous school year) - use the configured "Prior Year Exit Date" from the No Show Setup.** I recognize that STU.ED may not be the best way to perform the prior year enrollment check. I can think of a few ways... but Honestly, just find a method to determine if the student ended the prior year at the same school.
Having two No Show dates would align with the No Show Guidelines AND actually HELP users make the right choice!
-
7 votesChris Holloway
supported this idea
·
An error occurred while saving the comment Chris Holloway
commented
Very interesting....
We have been cleaning up the accent marks, but on a whim found some other Aeries Ideas... and decided to try myself.
It seems that the SINF file is being saved out from Aeries using the UTF-8 format (as shown in notepad).
However, when using the é character... that is extracted as something interesting a whitespace character ?? " " (i've pasted between the double-quotes).If I edit the SINF file and replace with the é character, the file processes just fine in CALPADS.
I believe there is some sort of issue with the Aeries SINF extract.
It would be nice to allow students to see their name as expected, with the proper accent marks.
-
55 votesChris Holloway
supported this idea
·
-
48 votesChris Holloway
supported this idea
·
-
141 votesChris Holloway
supported this idea
·
-
7 votes
An error occurred while saving the comment Chris Holloway
commented
This feels like a great idea... but also - so "high in the sky" that it is limiting any addressing of the current REAL challenge we are facing with poor search results!
We need a more immediate "low hanging fruit" resolution for the search results providing poor results.
See Support Ticket: 442318Chris Holloway
supported this idea
·
-
5 votesChris Holloway
shared this idea
·
-
3 votesChris Holloway
shared this idea
·
This occurred again. This time the process had not been running since April 17th.
I'm implementing my own logic to check for this... but i'm sure ALL hosted customers would benefit from a health check monitoring sub system.