Dec 2020 change request – feature highlights checklist

Lock empty shifts

1. Mark an empty shift as locked and unavailable for scheduling.  Shifts are locked one at a time.
2. Adjust personnel calculations on scheduler and dashboard.
3. Toggle locked empty shift to available

Mark shift as unavailable for a scheduled job

1. Wizard for marking shift as unavailable inside the job details view accessible by clicking the personnel link in the calendar
2. Workflow will require shift to be made up at the back end of the job and will require empty shifts to be available
3. Shift will be marked in red and will be unavailable for further scheduling

Job split

1. Create Y sub-jobs and prompt to enter quantity for each.  Auto name sub job as per naming convention.  Functionality will be implemented on list view to accommodate jobs not currently scheduled.
2. Reduce parent job quantity by sub-job quantity, remove parent job from scheduler and set status of both to split.
3. Total quantity of parent and all sub-jobs must always equal original quantity of parent.
4. Both parent and sub-jobs will show up in the need resolution view for scheduling.
5. Parent job will require rescheduling every time a new sub-job (or set of sub-jobs) is added.  This is because quantity of parent job has changed.  Previously created sub-jobs will not be affected.
6. Ignore Nulogy events for all split jobs, bot parent and sub-jobs.  This implies that Nulogy parameters will not override in these cases and the progress will not show on the dashboard.
7. Scheduler will display split jobs with a split icon (same as we do for lock)
8. Show all split jobs on separate view
9. Implement delete workflow for parent job where all dependent sub-jobs are also deleted
10. Implement delete workflow for sub-job where quantity of deleted sub-job is applied back to parent job (reverse of 2)
11. Auto lock sub-jobs when parent is locked.  Split jobs need to be manually locked by operator otherwise parent job will be automatically deleted on next forecast import.  If parent job is not locked in scheduler and is deleted then all sub-jobs will also be deleted from scheduler.
12. Implement quantity change business logic for split jobs where subsequent forecast changes the quantity of the parent job.
13. Implement ship date change business logic for split jobs.  Should parent job and all sub-jobs get set to “date change” state and be taken off schedule?  What if some of the sub-jobs are already completed?
14. Disallow split jobs from getting duplicated