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

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

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
65 26-Nov-2021 10:22 4 KB kparrott to previous
64 26-Nov-2021 10:22 4 KB kparrott to previous | to last
63 26-Nov-2021 10:22 4 KB kparrott to previous | to last
62 26-Nov-2021 10:22 4 KB kparrott to previous | to last NAGGING WORKFLOW LOG EMAILS ==> CONTINUOUS WORKFLOW LOG EMAILS
61 26-Nov-2021 10:22 4 KB jaiken to previous | to last PLANNING A WORK FLOW USERCALC ==> PLANNING A WORKFLOW USERCALC

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 40 added 3 lines
----
!!!Pro Active Work Flow
In the past, Work Flow required a table to be changed for it to be triggered. 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.
At line 44 added one line
One easy example of Pro Active Work Flow usage is to send out a Happy Birthday message to employees on their birthday. A where clause can be defined to filter all employee birth dates which are equal to the ‘As of’ date’s day and month. The user calc would call this work flow action and when the report [UMPWF] is run, an email would be generated to all of those employees with a birthday that day. The other method would have had the user calc filter the data, which is more tedious on the system.