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

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

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
31 26-Nov-2021 10:22 11 KB JEscott to previous
30 26-Nov-2021 10:22 11 KB JEscott to previous | to last
29 26-Nov-2021 10:22 11 KB RForbes to previous | to last
28 26-Nov-2021 10:22 11 KB JEscott to previous | to last DEFINE_WF_USERCALC ==> DEFINE WF USERCALC
27 26-Nov-2021 10:22 11 KB JEscott to previous | to last
26 26-Nov-2021 10:22 11 KB JEscott to previous | to last
25 26-Nov-2021 10:22 11 KB JEscott to previous | to last
24 26-Nov-2021 10:22 11 KB JEscott to previous | to last
23 26-Nov-2021 10:22 11 KB JEscott to previous | to last
22 26-Nov-2021 10:22 11 KB JMyers to previous | to last
21 26-Nov-2021 10:22 11 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
DEFINE WF USERCALC
DEFINE WF USERCALC

Version management

Difference between version and

At line 1 added one line
[{TableOfContents }]
At line 3 added 7 lines
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|MODULE-UC]manual for a more thorough explanation of UserCalcs and their functionality.
At line 10 changed 4 lines
;[User Calc|USERCALC]:
This field refers to the user-defined name given to the UserCalc.
Once the UserCalc has been created it can be edited, however, you can not edit it once the UserCalc is in production. You have to Un-Publish it on IMUCA first.
As with Benefit and Attendance UserCalcs, we recommend that a naming convention be used for Workflow UserCalcs. For example, AT is used for the Attendance application, BE for the Benefits application and WF for the Workflow application. This will allow for efficient queries once the UserCalc list becomes large.
;[User Calc|USER_CALC_CODE]:This field refers to the user-defined name given to the UserCalc.;:Once the UserCalc has been created it can be edited, however, you can not edit it once the UserCalc is in production. You have to Un-Publish it on IMUCA first.
%%information As with Benefit and Attendance UserCalcs, we recommend that a naming convention be used for Workflow UserCalcs. For example, AT is used for the Attendance application, BE for the Benefits application and WF for the Workflow application. This will allow for efficient queries once the UserCalc list becomes large.%%
At line 19 changed 3 lines
The product indicates which module the UserCalc has been defined for. For example, PR-Payroll, BE-Benefits, AT- Attendance, FC-Forecasting & Costing and WF-Workflow.
See that table list on page 10 of this manual for all of the work flow product areas supported at the current time with the name of the table that triggers that product.
With respect to Workflow, this field specifies the table code on which the workflow trigger is located. This field should be identical to the name of the "Table" in IMWA. In all cases except workflow, it is the application that controls which fields in which tables will be accessible by the UserCalc. For example, in an Attendance UserCalc, the Leave Accrual Table would be accessible, but not benefits information.
The product indicates which module the UserCalc has been defined for. For example, PR-Payroll, BE-Benefits, AT- Attendance, FC-Forecasting & Costing and WF-Workflow.%%information With respect to Workflow, this field specifies the table code on which the workflow trigger is located. This field should be identical to the name of the "Table" in IMWA. In all cases except workflow, it is the application that controls which fields in which tables will be accessible by the UserCalc. For example, in an Attendance UserCalc, the Leave Accrual Table would be accessible, but not benefits information.%%
At line 23 changed 7 lines
;[Status|st
This field describes the status of the UserCalc. The following values are available.
Under Construction This status value indicates that the UserCalc has not been completed and therefore will not be published.
Being Tested This status value indicates that the UserCalc has been completed, compiled and is being tested by the user who created it. It will not be published.
To Be Published This status value indicates that the UserCalc is ready for publishing. You can not set the user calc to this value manually.
In Production This status value indicates that the UserCalc has already been published and is in use.
Pre-Compiled This status is now obsolete and will be removed in a future version.
;[Status|STATUS]:This field describes the status of the UserCalc. The following values are available.
|Under Construction|This status value indicates that the UserCalc has not been completed and therefore will not be published.
|Being Tested|This status value indicates that the UserCalc has been completed, compiled and is being tested by the user who created it. It will not be published.
|To Be Published|This status value indicates that the UserCalc is ready for publishing. You can not set the user calc to this value manually.
|In Production|This status value indicates that the UserCalc has already been published and is in use.
|Pre-Compiled|This status is now obsolete and will be removed in a future version.
At line 31 changed 5 lines
;[Type|
This field defines what values may be passed or used between UserCalcs and what capabilities may be performed. There are three types available:
Calculations These are used by the main program and may call Qualifiers and Functions in order to perform a customized action or operation. The Payroll, Forecasting & Costing and Workflow modules exclusively use calculations.
Qualifiers These are used to reduce the number or employees or calculations processed by the UserCalc.
Functions These are used to perform a calculation or query and return a value to the calculation. The Benefits and Attendance modules exclusively use "Functions".
;[Type|TYPE]:This field defines what values may be passed or used between UserCalcs and what capabilities may be performed. There are three types available:
|Calculations|These are used by the main program and may call Qualifiers and Functions in order to perform a customized action or operation. The Payroll, Forecasting & Costing and Workflow modules exclusively use calculations.
|Qualifiers|These are used to reduce the number or employees or calculations processed by the UserCalc.
|Functions|These are used to perform a calculation or query and return a value to the calculation. The Benefits and Attendance modules exclusively use "Functions".
At line 37 changed 4 lines
;[Return Value|
The "Return Value" is used by Functions and Qualifiers to define what type of value will be returned by the Function or Qualifier UserCalc.
If the UserCalc type is set to Calculation, then no return value is indicated. This field will automatically be grayed out once this type has been selected and the cursor has been tabbed to the next field.
Since workflow UserCalcs are always of the type "Calculation", they will not return a value.
;[Return Value|RETURN_VALUE_TYPE]:The "Return Value" is used by Functions and Qualifiers to define what type of value will be returned by the Function or Qualifier UserCalc.;:If the UserCalc type is set to Calculation, then no return value is indicated. This field will automatically be grayed out once this type has been selected and the cursor has been tabbed to the next field.;:Since Workflow UserCalcs are always of the type "Calculation", they will not return a value.
At line 42 changed 5 lines
;[Usage|
This field is optional but can add additional definition to how/when this user calc should function. There are three entries to select from:
Not Specified Use this or leave it blank for most purposes.
Disbursement Message Not used for Work Flows - see the user calc manual for more details on this usage.
Secondary WF This option tells the Work Flow engine that this User Calc is ONLY to be called from another user calc and should NOT be fired on its own by the triggering product.
;[Usage|]:This field is optional but can add additional definition to how/when this UserCalc should function. There are three entries to select from:
|Not Specified|Use this or leave it blank for most purposes.
|Disbursement Message|Not used for Work Flows - see [UserCalc|MODULE-UC] for more details on this usage.
|Secondary WF|This option tells the Work Flow engine that this UserCalc is ONLY to be called from another UserCalc and should NOT be fired on its own by the triggering product.
At line 48 changed 4 lines
;[Compile UserCalc SQL|
This button allows the user to check the syntax of a UserCalc by generating the PL/SQL code that is used behind the scenes.
This step does not ensure accuracy of the UserCalc. It merely checks that there are no UserCalc language
errors such as incorrect syntax or infinite loops.
;[Compile UserCalc SQL|]:This button allows the user to check the syntax of a UserCalc by generating the PL/SQL code that is used behind the scenes.:;This step does not ensure accuracy of the UserCalc. It merely checks that there are no UserCalc language errors such as incorrect syntax or infinite loops.
At line 53 changed 2 lines
;[Publish UserCalc|
This button preps the UserCalc for Publishing and sets the status as "To Be Published".
;[Publish UserCalc|]:This button preps the UserCalc for Publishing and sets the status as "To Be Published".
This page (revision-31) was last changed on 26-Nov-2021 10:22 by JEscottTop