This page (revision-29) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by rforbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
29 26-Nov-2021 10:22 3 KB kparrott to previous
28 26-Nov-2021 10:22 3 KB kparrott to previous | to last
27 26-Nov-2021 10:22 3 KB tchau to previous | to last
26 26-Nov-2021 10:22 3 KB jaiken to previous | to last SOP.HR Nightshift ==> HR Nightshift
25 26-Nov-2021 10:22 3 KB ihowie to previous | to last
24 26-Nov-2021 10:22 3 KB ihowie to previous | to last
23 26-Nov-2021 10:22 3 KB ihowie to previous | to last
22 26-Nov-2021 10:22 2 KB ihowie to previous | to last
21 26-Nov-2021 10:22 2 KB ihowie to previous | to last

Page References

Incoming links Outgoing links
HR Nightshift...nobody
HR Nightshift

Version management

Difference between version and

At line 3 added one line
# reduce employee time to run functions that can be monitored after the fact freeing up time for more important tasks
At line 9 changed one line
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.
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.
At line 11 changed one line
Additional functions can be added to this base schedule for specific site requirements maintaining the process flow.
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.
At line 15 changed 5 lines
|''0130'' |UDAP| Maintain Approval Records
|''0145'' |UEPL| Maintain People Lists
|''0200'' |UMPWPF| Start Pro-Active Work Flow
|''0215'' |UMPWF| Start Pro-Active Work Flow
|''0600'' |RMWF| Work Flow Actions Report
|''0130'' |UEPL| Maintain People Lists
|''0145'' |UDAP| Maintain Approval Records
|''0200'' |UMPWF| Start Pro-Active Workflow 1
|''0215'' |UMPWF| Start Pro-Active Workflow 2
|''0600'' |RMWF| Workflow Actions Report
At line 22 added 2 lines
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.
At line 31 changed one line
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 work flow may have made that change. Proactive Workflows then will create any emails that they are required to produce to be sent.
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.
At line 34 changed one line
This function will group any outstanding workflow emails that need to be bundled and sent to employees.
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.
This page (revision-29) was last changed on 26-Nov-2021 10:22 by kparrottTop