Option to Require Date Last Attended on Faculty Self Service when submitting Grades
I know we already put so many RPEs on the Sungardhe support site for this. Has anyone looked into it. Basically our Financial Aid Office Just wants to know if a student who got an F or non-passing grade attended after a certain date. We were thinking that when an instructor submitted the grades, we would show a pop up with a list of those students who got non-passing grades and a couple of check boxes for each. We ask the instructor if the student attended past Nov 2 and when they fill out the checkboxes and submit the procedure will insert this information into our own table and continue with the commit procedure. Does this seem to far fetch? has anyone tried anything.
Also where is that MSG_LABEL that contains "The changes you made were saved successfully".
I am barely going into Luminis and SSB and would really appreciate any help.
I have been looking in BANINST1 AND SYS schemas.
Thanks
What about a trigger on the table?
I'm just wondering out loud, but isn't the date last attended a field on the grade entry screen in Self-Service? So, depending on your web-user name, you could build a trigger that fired on the underlying table that when the web user submitted the grades, and any grade was an F without an attendance date would cause an error. The catch there would be this: what does the error look like to the end-user, and is it clear the grades were NOT submitted because of the error... but it might be a start.
Otherwise, you're going to have to build a new page that asks for this information, and modify the grade entry page to point to it if the conditions exist. Depending on your mod/no-mod policy, the trigger may be the better way..
We're also using the Hours Attended field to flag if they ever showed up in the course at all, which is important to us. 0 means they never showed up, and 1 means they attended at least once...
Re: Option to Require Date Last Attended on Faculty Self Service
Our first stab at this was a simple modification to student/dbprocs/shkegr1.sql. In shkegrb.P_CommitFinGrd() there is a loop that cycles through each student submitted. I simply put the grade/attend date checking at the beginning of this loop and break out of the loop if there is an error. The side effect of this, however, is that when a faculty member submits a completed form and there is an error, entries from the point of the error and down are erased from the form. This requires them to re-enter the information which can be time consuming.
I've been asked to fix this issue so I'll be revisiting this bit of code in the near future. I'll keep you posted with updates.
Been there, man
I was tasked with this recently as well. The problem we had with pop ups was pop-up blockers on the clients. What I ended up doing is making a small mod to the baseline grade form to set the form action to a new custom form. The new custom form handles all the data checking (not only do they have me checking F grades/last attendance, but I'm also checking for I grades and requiring the submission of a form). Once all their conditions are met, then the program re-routes the data back to the original form action from the baseline grade form. Since all these things occur between the grade form and before the baseline grade submission through a custom ssb page, we have minimal changes made to the baseline code (the form action), we avoid popups, and we can control the data to all the crazy extents we want.
We did have to change one of the error messages to a success message with web tailor, since having a date of last attendance for a student who didn't withdraw returns a warning instead of a success message. The procedure was bwlkffgd.P_FacFinGrd, and the info text item was NOT_WITHDRAWN. We changed the label to read the same as the NO_ERROR text item.
If you'd like, I can take out the pieces that apply to some of our own requirements and just leave in the part about F grades/last attendance. Not sure what the rules are for posting code on the forum? (or would it be a security risk because it shows table structure in banner?)