Skip to content
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

Enhance the Term TDTM logic to update Course Offering dates when Term dates are updated in more scenarios #871

Open
robertbwatson opened this issue Jul 19, 2019 · 0 comments
Labels
enhancement Improving upon existing functionality

Comments

@robertbwatson
Copy link
Contributor

Note: FOR INTERNAL USE ONLY. For support questions, please use the EDA Chatter group in The Power of Us Hub.
For feature requests, please use the Ideas tab in The Power of Us Hub.

  • Do you want to request a feature or report a bug?
    Feature/Enhancement

  • What is the current behavior?
    When a Term's Start and/or End Date is updated, the new values are only copied down to the child Course Offering(s) when:

  1. The Term Start Date or End Date was previously blank, and
  2. The Course Offering Start Date or End Date is currently blank
  • What is the expected behavior?
    It would be an improvement if EDA also looks at changes to the Term's Start and/or End Dates when the date(s) are being changed from one value to another value (for example, the term might now end on June 24th instead of June 22nd because of a prior weather emergency)

In this instance, EDA would look for Course Offering(s) where the Start Date and End Date matches the previous values of the Term and updates them to match the new values of the Term.

  • What is the motivation / use case for changing the behavior?
    Data integrity
@robertbwatson robertbwatson added the enhancement Improving upon existing functionality label Jul 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving upon existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant