Menu

#2413 Schedules longer than two years not applied/visible

RELEASE_12_1
open-accepted
nobody
None
5
2014-10-07
2013-03-29
No

Problem Summary:
It you try to create a schedule that is greater than two years, it does not apply the schedule for the provider after two years.

Expected Result:
The schedule should be set for the date range entered - regardless of the date range.

Actual Result:
The schedule stops after two years.

Steps to Reproduce:
(1) Create a schedule template - through Admin-->Schedule-->Schedule Setting
(2) Apply the template to a provider - through Admin-->Schedule-->Schedule Setting
(3) In the "Date from" enter 2014-01-01. In the "Date to" enter 2017-12-31.
(4) Go to 2017-01-01 on the Schedule Screen. The schedule template will not appear - it will show the provider as "not on schedule".
(5) Go back to Admin-->Schedule-->Schedule Setting and look at the schedule for the provider again. The schedule still shows 2014-01-01 to 2017-12-31.

Reproduced In:
12_1 Deb 362 (fresh install) + Ubuntu 12 LTS (fresh install)

Additional Information:
* The scheduledate table does not contain the right entries. It should contain one entry for each day in the schedule - it stops at 2015-12-31.
* The rschedule table does indicate the right start and end date for the schedule - in the sdate and edate columns.

Discussion

  • Victor Van Herk

    Victor Van Herk - 2013-05-22
    • assigned_to: nobody --> vanherk
     
  • Victor Van Herk

    Victor Van Herk - 2013-05-28

    Solution will be to:
    - make schedule duration configurable from the config file.
    - fail the operation if user attempts to create schedule longer then configured.

     
  • Trimara Corporation

    • Group: --> RELEASE_12_1
     
  • Trimara Corporation

    • summary: Schedules Longer than Two Years Not Applied/Visible --> Schedules longer than two years not applied/visible
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -10,13 +10,13 @@
     Steps to Reproduce:
     \(1\) Create a schedule template - through Admin-->Schedule-->Schedule Setting
     \(2\) Apply the template to a provider - through Admin-->Schedule-->Schedule Setting
    -\(3\) In the "Date from" enter 2013-01-01. In the "Date to" enter 2016-12-31.
    -\(4\) Go to 2015-01-01 on the Schedule Screen. The schedule template will not appear - it will show the provider as "not on schedule".
    -\(5\) Go back to Admin-->Schedule-->Schedule Setting and look at the schedule for the provider again. The schedule still shows 2013-01-01 to 2016-12-31.
    +\(3\) In the "Date from" enter 2014-01-01. In the "Date to" enter 2017-12-31.
    +\(4\) Go to 2017-01-01 on the Schedule Screen. The schedule template will not appear - it will show the provider as "not on schedule".
    +\(5\) Go back to Admin-->Schedule-->Schedule Setting and look at the schedule for the provider again. The schedule still shows 2014-01-01 to 2017-12-31.
    
     Reproduced In:
    -12\_1 Deb 95 \(fresh install\) + Ubuntu 12 LTS \(fresh install\)
    +12\_1 Deb 362 \(fresh install\) + Ubuntu 12 LTS \(fresh install\)
    
     Additional Information:
    -\* The scheduledate table does not contain the right entries. It should contain one entry for each day in the schedule - it stops at 2014-12-31.
    +\* The scheduledate table does not contain the right entries. It should contain one entry for each day in the schedule - it stops at 2015-12-31.
     \* The rschedule table does indicate the right start and end date for the schedule - in the sdate and edate columns.
    
    • Priority: 5 --> 7
     
  • Victor Van Herk

    Victor Van Herk - 2014-04-18
    • assigned_to: Victor Van Herk --> nobody
     
  • SBek

    SBek - 2014-07-15
    • status: open --> open-accepted
     
  • SBek

    SBek - 2014-07-15

    The issue has been replicated on both R12.1 (build #415) and Master (build #2068)

     
  • SBek

    SBek - 2014-10-07

    Downgrading the priority as temporary workaround is available (set schedule to < 2 years for now)

     
  • SBek

    SBek - 2014-10-07
    • Priority: 7 --> 5
     
MongoDB Logo MongoDB