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
CONFIGURATION-WF
CONFIGURATION-WF

Version management

Difference between version and

At line 5 changed one line
Workflow triggers are initiated when a record is inserted, updated or deleted from the database. Each table that is enabled for workflow will have a [data base trigger|DATA BASE TRIGGER] configured.
Workflow triggers are initiated when a record is inserted, updated or deleted from the database. Each [table|WORKFLOW PRODUCTS] that is enabled for workflow will have a [data base trigger|DATA BASE TRIGGER] configured.
At line 7 changed one line
The page [Workflow Tables|WORKFLOW PRODUCTS] will list each table that has workflow enabled.
* [USERCALCS in Workflows]
* [Tables that Workflow acts on|WORKFLOW PRODUCTS]\\ \\
At line 16 changed 2 lines
*[Nagging Workflow Log Emails|CONTINUOUS WORKFLOW LOG EMAILS]
*Workflow Actions Report ([RMWF])
*[WF Emails That Cannot Be Sent|WF Emails That Cannot Be Sent]
*[Nagging Work Flow Log Emails|NAGGING_WORKFLOW_LOG_EMAILS]
*[Report on Workflow Actions|REPORT_ON_WORKFLOW_ACTIONS]
*[Emailing Batched Workflow Logs|EMAILING_BATCHED_WORKFLOW_LOGS] \\ \\
At line 19 removed one line
At line 35 changed one line
* [Planning a Workflow UserCalc|PLANNING A WORKFLOW USERCALC|PLANNING A WORKFLOW USERCALC]
* [Planning a Work Flow UserCalc|PLANNING A WORK FLOW USERCALC]
At line 38 changed one line
* [Defining a WF UserCalc|DEFINE WF USERCALC]
* [Defining a WF UserCalc|DEFINING A WF USERCALC]
At line 40 removed 3 lines
----
!!!Pro Active Workflow
In the past, Workflow required a table to be changed for it to be triggered. 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 44 removed one line
One easy example of Pro Active Workflow 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 workflow 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.
At line 46 changed one line
*Define Workflow Action ([IMWA])
!Define User Calcs
The other component of workflow requires setting up the UserCalc to incorporate the action event created in [IMWA]. The integration of workflow required some additional functionality that was not previously available to UserCalcs. This section should be used as a supplemental aid to the User Calculations manual and is not to be used in place of it. Please refer to the [User Calculations|USERCALC] section for a more thorough explanation of UserCalcs and their functionality.
*[Define Workflow UserCalc|DEFINE WF USERCALC]
**[Lines Tab|DEFINE WF USERCALC#Lines Tab]
At line 48 changed 5 lines
*Plan and Define a User Calc ([IMUC])
**The user calcs used in Pro Active Workflow must be defined with a usage of Pro-Active WF for them to be picked up by the [UMPWF].
* Create a Where Clause ([IMWC])
* Run [UMPWF]
* [Examples of Pro-Active Workflow|PRO ACTIVE WORKFLOW EXAMPLES]
!Publish User Calculations
The putting of UserCalcs into production is controlled in Publish User Calculations [IMUCA]. The administration of UserCalcs also involves an expanded knowledge of the status of UserCalcs. Please refer to the [User Calculations|USERCALC] section for a more detailed explanation.
At line 52 added 3 lines
%%information Once a workflow UserCalc has been put "In Production" to stop it from firing you not only have to "UNPUBLISH" it but also then set its status back to "Under Construction".%%
*[Publishing UserCalcs|PUBLISHING USERCALCS]
At line 62 changed one line
*[IMST Setup for Workflow|IMST SETUP FOR WF]
*[IMST Setup for Workflow|IMST_SETUP_FOR_WF]
At line 68 removed 5 lines
----
![Notes|Edit:Internal.CONFIGURATION-WF]
[{InsertPage page='Internal.CONFIGURATION-WF' default='Click to create a new notes page'}]
This page (revision-65) was last changed on 26-Nov-2021 10:22 by kparrottTop