Current limitation from the Rolling schedule should not be allowed to have different settings for each scenario within a Schedule, which currently is allowed and does not make sense, we need to make the settings the same for all scenarios of a schedule

• Each scenario can have different Schedule dates and we will continue to allow this for schedules without rolling projects set to on.

• Rolling schedule needs further cleanup in order to make it easier for the user to understand what will happen when turned on.

• Crons that automatically roll can be set up at a scenario basis and refreshing the other scenarios will align them again as the dates will change for all of them. • GWW, GS, GS-LP, GA, GA-RF are all effected

One Dialog

• Moving all the Rolling requirements into one dialog will make it clearer to the user what and when the action Roll Schedule will do to the start dates and when it will happen

• Allow the user to run immediately or save the cron set up info for rolling the schedule.

• Currently when user opens the Recurring schedule dialog it defaults to every 1 day at 12am 

• If the Recurring is blank the Copy value from parameter

Display the Rolling Offset in Days field into the dialog – can we allow them to edit this field in either dialog?

• Preview will now use the Rolling offset in days to preview the correct next dates

• Preview title change from “Date Preview” to “Next schedule start dates” for GS,GSLP, GWW, GA, GA-RF or “Next work list start dates” for GWW, GA, GA-RF • Also, the time selected is not shown in preview and isn’t set to that time when rolled

Roll setup – Keep all scenarios in sync

 When Rolling schedule is set off

• no changes will occur with current logic

• This allows the user to have different start and end dates for each scenario When Rolling schedule is set on

• All scenarios in the schedule including the default scenario will have the same values on creation or change in the following fields

• All SKDPROJECT records for this schedule(NAME) have the same values for ROLLING, ROLLDATESCHEDULE, DURATION, ROLLOFFSET fields

• Existing customers will get this new logic as the current logic is really a defect and could cause other issues throughout the applications Roll action - immediately or on cron

• Roll must change the schedule/work list start and end dates for all scenarios where the SKDPROJECT.NAME is the same as the scenario that is being rolled SKDPROJECT.NAME

• If cron is setup to roll SKDPROJECTID 12 – it will change the dates for records 10 and 18 as well –Time will not be updated once that affects modify

 • If refresh data is on the cron will only refresh SKDPROJECTID 12 and not the other scenarios, this will be left to the user to refresh manually