This page (revision-8) 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
8 26-Nov-2021 10:22 892 bytes kparrott to previous
7 26-Nov-2021 10:22 895 bytes rforbes to previous | to last PROACTIV WF LIMIT(System_Preference) ==> PROACTV_WF_LIMIT(System_Preference)
6 26-Nov-2021 10:22 895 bytes rforbes to previous | to last
5 26-Nov-2021 10:22 899 bytes jmyers to previous | to last
4 26-Nov-2021 10:22 936 bytes jmyers to previous | to last PROACTIV_WF_LIMIT ==> PROACTIV WF LIMIT(System_Preference)
3 26-Nov-2021 10:22 936 bytes jmyers to previous | to last
2 26-Nov-2021 10:22 753 bytes jmyers to previous | to last
1 26-Nov-2021 10:22 698 bytes RForbes to last

Page References

Incoming links Outgoing links
PROACTV_WF_LIMIT(System_Preference)
PROACTV_WF_LIMIT(System_Preference)

Version management

Difference between version and

At line 2 changed one line
This will control the number of records that a pro-active work flow will process. If not set, the default value is 100.
This will control the number of records that a pro-active workflow will process. If not set, the default value is 100.
At line 4 changed one line
The intent of this preference setting is to prevent a run-away work flow process from overwhelming the system. For example, a work flow that sends an email birthday greeting to an employee but does not have a conditioning [where clause|WHERE_CLAUSE] to control who gets the email may result in all employees getting this message every time that the [UMPWF] function is executed. If the UMPWF function executes regularly on a scheduled basis, this would quickly overwhelm the system.
The intent of this preference setting is to prevent a run-away workflow process from overwhelming the system. For example, a workflow that sends an email birthday greeting to an employee but does not have a conditioning [where clause|WHERE_CLAUSE] to control who gets the email may result in all employees getting this message every time that the [UMPWF] function is executed. If the UMPWF function executes regularly on a scheduled basis, this would quickly overwhelm the system.
This page (revision-8) was last changed on 26-Nov-2021 10:22 by kparrottTop