-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggested Update #105
Comments
Ok, so let's say that a student registers for a course after the term start date. He or she registers for a course on Monday, and then registers for a course on Thursday. If a business rule is set for this, the fee will be added to the student's bill twice because of the two different registrations. This is the only way I can see it work. Are you ok with that? Also, does drop/add play a part in this as well? |
Thanks for the prompt response. (2) Our registration period ends well before the drop/add day, so it is not in play. However, if you suggest that drop/add should be the same day as the closing of registration, we can do that. Right now we are using drop/add date as the last date to drop a course without academic penalty. If this is not SOP for the drop/add function, we can adjust. Thanks for all you do! |
(2) No, that is not necessary. Just needed to know in case I needed to make some other change. |
This is not going to be possible. There is no appropriate date field that will fit within the current login. I am keeping this issue open in case something changes or something new comes along. |
Thanks for looking into it. |
We normally charge a late fee for late registration period. It would be great if there was an option to create a business rule where any student that registers between two different dates OR after the start date of the term, can be charged a late fee if/when the student register for class late. Could it be added to the business rules of the billing table?
Just a thought
The text was updated successfully, but these errors were encountered: