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 5 changed one line
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.
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.
At line 7 changed 2 lines
* [USERCALCS in Workflows]
* [Tables that Workflow acts on|WORKFLOW PRODUCTS]\\ \\
The page [Workflow Tables|WORKFLOW PRODUCTS] will list each table that has workflow enabled.
At line 10 changed one line
!!Workflow Action
!!!Workflow Action
At line 13 changed one line
*[Define Workflow Action|IMWA]
*Define Workflow Action ([IMWA])
At line 16 changed 4 lines
*[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] \\ \\
*[Nagging Workflow Log Emails|CONTINUOUS WORKFLOW LOG EMAILS]
*Workflow Actions Report ([RMWF])
At line 21 changed one line
!!UserCalcs and Workflow
!!!UserCalcs and Workflow
At line 26 changed 4 lines
With the integration of workflow into the system, UserCalcs have the ability, in addition to their previous
functionality, to allow for workflow action events to occur under specific conditions. Examples of such events
include: issuing an email, alerting users of specific tasks and taking the user to that particular screen to
complete the task. Workflow action events are only processed through UserCalcs.
With the integration of workflow into the system, UserCalcs have the ability, in addition to their previous functionality, to allow for workflow action events to occur under specific conditions. Examples of such events include: issuing an email, alerting users of specific tasks and taking the user to that particular screen to complete the task. Workflow action events are only processed through UserCalcs.
At line 31 changed 3 lines
!Purpose of UserCalcs
A UserCalc is a set of instructions, defined by the user, which trigger specific actions or
operations to take place.
A UserCalc is a set of instructions, defined by the user, which trigger specific actions or operations to take place. They are a powerful feature that allows for configuration of the application to a high degree.
At line 35 changed 4 lines
They are a powerful feature that allows for customization of the application to a high degree.
UserCalcs can perform various operations, such as arithmetic calculations, comparisons of
different items, date checks and calculations, issue warning messages and workflow action
events.
UserCalcs can perform various operations, such as arithmetic calculations, comparisons of different items, date checks and calculations, issue warning messages and workflow action events. UserCalcs can be simple or quite complex.
At line 40 changed one line
UserCalcs can be simple or quite complex.
The activation of a workflow trigger results in the initiation of a UserCalc. Once the UserCalc is initiated, the workflow action events are called from within the UserCalc.
At line 42 changed 8 lines
!Workflow
The activation of a workflow trigger results in the initiation of a UserCalc. Once the UserCalc is
initiated, the workflow action events are called from within the UserCalc.
*[How to Plan a Workflow UserCalc|HOW_TO_PLAN_A_WORKFLOW_USERCALC]
*[UserCalc Conventions|USERCALC_CONVENTIONS]
*[UserCalc Types|USERCALC TYPES]%%information Workflow is only concerned with Calculation types.%%
\\
* [Planning a Workflow UserCalc|PLANNING A WORKFLOW USERCALC|PLANNING A WORKFLOW USERCALC]
* [UserCalc Conventions|USERCALC CONVENTIONS]
* [UserCalc Types|USERCALC TYPES]
* [Defining a WF UserCalc|DEFINE WF USERCALC]
* [Publishing a WF UserCalc|PUBLISHING A WF USERCALC]
At line 51 changed 8 lines
!!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]
\\ \\
----
!!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.
!!!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 60 changed one line
%%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".%%
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 62 changed 2 lines
*[Publishing UserCalcs|PUBLISHING_USERCALCS]
\\ \\
*Define Workflow Action ([IMWA])
*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]
At line 65 changed 12 lines
!! View Execution Logs & Details
*[View Execution Logs & Details|VIEW_EXECUTION_LOGS]
*[VMEX]
\\ \\
----
!!Required Set Up
*[IMST Setup for Workflow|IMST_SETUP_FOR_WF]
\\ \\
----
!!Functions for Forecasting and Costing
Here are some other points or information to help make your use of workflow a success.
%%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 you need to set its status back to be "Under Construction".%%
!!! View Execution Logs & Details
At line 78 changed 3 lines
*[UserCalc Usage - Secondary WF|USERCALC_USAGE_SECONDARY_WF]
*[Comparison of Null Values|COMPARISON_OF_NULL_VALUES]
\\ \\
*View Execution Run Logs ([VMEX])
At line 82 changed 20 lines
!!Workflow Samples
* [A New Hire Workflow Procedure|WF SAMPLE 01]
* [Print Screens of Workflow Action Setup|WF SAMPLE 02]
* [Set Up Of Workflow Usercalc|WF SAMPLE 03]
* [Update the Job Seniority Date Field|WF SAMPLE 04]
* [Send An Email To The Manager At Specific Time Intervals|WF SAMPLE 05]
* [Sending An Email To A Specific Identity|WF SAMPLE 06]
* [Update A Field|WF SAMPLE 07]
\\ \\
----
!!Available WF Custom Functions
*[For All Work Flow Products|AVAILABLE_WF_CUSTOM_FUNCTIONS]
*[For Work Flow Product - WF_AAL|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_AAL]
*[For Work Flow Product - WF_EASD|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_EASD]
*[For Work Flow Product - WF_EEM|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_EEM]
*[For Work Flow Product - WF_RAP|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_RAP]
*[For Work Flow Product - WF_RASE|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_RASE]
*[For Work Flow Product - WF_RCA|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_RCA]
*[For Work Flow Product - WF_SPA|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_SPA]
*[For Work Flow Product - WF_TRE|AVAILABLE_WF_CUSTOM_FUNCTIONS#For Work Flow Product - WF_TRE]
!!!Required Set Up
At line 62 added 11 lines
*[IMST Setup for Workflow|IMST SETUP FOR WF]
----
![Notes|Edit:Internal.CONFIGURATION-WF]
[{InsertPage page='Internal.CONFIGURATION-WF' default='Click to create a new notes page'}]