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

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

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
7 26-Nov-2021 10:22 2 KB kparrott to previous
6 26-Nov-2021 10:22 2 KB kparrott to previous | to last
5 26-Nov-2021 10:22 2 KB kparrott to previous | to last
4 26-Nov-2021 10:22 2 KB jmyers to previous | to last WORKFLOW_TRACE ==> WORKFLOW_TRACE(System_Preference)
3 26-Nov-2021 10:22 2 KB JMyers to previous | to last
2 26-Nov-2021 10:22 2 KB JEscott to previous | to last
1 26-Nov-2021 10:22 1 KB JEscott to last

Page References

Incoming links Outgoing links
UMPWF
UMPWF

Version management

Difference between version and

At line 1 changed one line
!!!START PRO-ACTIVE WORK FLOW
!!!START PRO-ACTIVE WORKFLOW
At line 9 changed one line
If no user calculation is defined, then the process will fire all of the pro-active workflow user calculations defined for the product in focus.
If no User Calc is defined, then the process will fire all of the pro-active workflow User Calcs defined for the product in focus.
At line 11 changed one line
Any user calc messages will appear in the report. This may help in the case of user calcs not firing as expected. This new process, Pro Active Work Flow, enables Work Flow to be scheduled. Pro Active Work Flow uses where clauses to filter the data to help reduce the number of records that will qualify for the work flow to fire against.
Any User Calc messages will appear in the report. This may help in the case of User Calcs not firing as expected. This new process, Pro Active Workflow, enables Workflow to be scheduled. Pro Active Workflow uses where clauses to filter the data to help reduce the number of records that will qualify for the workflow to fire against.
At line 13 changed one line
UMPWF is run for a workflow user calc code and for a where clause.
UMPWF is run for a workflow User Calc code and for a where clause.
%%information It should be noted that the User Calc being called should not attempt to update field values. Pro-active workflows can only be used to iniate workflow actions defined on the [IMWA].
On [IMST] there is a preference called PROACTIV_WF_LIMIT. This is used to identify the maximum number of records that a pro-active workflow can process. If not defined, it defaults to 100.
If the number of records being processed exceeds this number, then UMPWF will not complete. This is why most of the records to be examined should be determined at the Where Clause level rather than the User Calc level.%%
At line 19 changed one line
|User Calc Code|This is an optional field. This indicates what user calc is to be called to trigger the work flow action. Only user calcs defined with a [usage|USER_CALC_USAGE] of Pro Active will be displayed.
|User Calc Code|This is an optional field. This indicates what user calc is to be called to trigger the workflow action. Only user calcs defined with a [usage|USER_CALC_USAGE] of Pro Active will be displayed.
At line 21 changed one line
|Exception Level|The user must select an exception level to run the report. This will determine the amount of trace that will be displayed to the employee. . The [WORKFLOW_TRACE] preference should be set to at least 0 or 01 to see any data in the report. If users are having trouble and are not getting the desired results, increase the workflow trace in [IMST] to a higher value ( ie 9 and retest the report). Be sure to decrease the trace level when you are finished so there is no performance impact on the rest of the system.
|Exception Level|The user must select an exception level to run the report. This will determine the amount of trace that will be displayed to the employee. The [WORKFLOW_TRACE(System_Preference)] preference should be set to at least 0 or 01 to see any data in the report. If users are having trouble and are not getting the desired results, increase the workflow trace in [IMST] to a higher value ( ie 9 and retest the report). Be sure to decrease the trace level when you are finished so there is no performance impact on the rest of the system.
At line 24 removed 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 27 changed 4 lines
![Discussion|Edit:Internal.UMPWF]
[{InsertPage page='Internal.UMPWF' default='Click to create a new discussion page'}]
}]
![Notes|Edit:Internal.UMPWF]
[{InsertPage page='Internal.UMPWF' default='Click to create a new notes page'}]
This page (revision-7) was last changed on 26-Nov-2021 10:22 by kparrottTop