The purpose with this series of functions scheduled in an overnight period is to:

1. to make use of unused processing time in a traditionally slow period of usage
2. reduce employee time to run functions that can be monitored after the fact freeing up time for more important tasks
3. to maintain current HR changes to employees
4. maintain any outstanding Approval Processes
5. provide current relevant email notifications.

Typically in a daily environment most processing and functionality is done during normal business hours. This series of scheduled tasks will help with items that can be monitored after the fact. These tasks are scheduled in the middle of the night at a point after any daily database backups have completed. The purpose of this is to allow a safe restore point prior to the functions being run should an issue arise.

For purposes of this example we will assume that the daily database backups complete at 0030 each night and that the normal work day starts at 0800 each day when the majority of employees begin their day. The following functions are scheduled to run each night. Your schedule can be adjusted for your available time window.

Additional functions can be added to this base schedule for specific site requirements maintaining the process flow. Note that it is recommended that each scheduled process be run at its own individual time slot to allow for easier after the fact troubleshooting should any be required.

Scheduling Note for From and To Dates. When scheduling an report or update to be run the relative date fields are used in place of actually providing a date. This would mean that the Beginning of Day with or without a +- field would be entered in the Report Parameters.

USPPA This function will update any approved but not processed Personal Actions in the database. These may have been approved but the user did nto hit the second process PA button to actually apply the changes to the employees involved.

UDAP Once any PA changes have been applied to the database by USPPA the UDAP process will automatically re evaluate any outstanding approvals to determine if there has been a change in who it should be assigned to. Example a manager is moved from one department to another and an employee in the old department has requested a vacation day, this should now be approved by the new manager and not the old manager that has now moved to a new department.

UEPL This function would update an existing people list similar to manually going to IMPL and hitting the update details button.

UMPWF This function is scheduled once for each pro active workflow that needs to run. A different time is used for each pro active workflow to allow for easier troubleshooting to determine what time a change was made and which workflow may have made that change. Proactive Workflows then will create any emails that they are required to produce to be sent.

RMWF This function will group any outstanding workflow emails that need to be bundled and sent to employees. This function is typically run without Report Filters so that any outstanding actions are completed.