This page (revision-41) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

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
41 26-Nov-2021 10:22 10 KB Kevin Higgs to previous

Page References

Incoming links Outgoing links
IMUC
IMUC

Version management

Difference between version and

At line 8 changed one line
;[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. 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. See [special characters|Naming Convention] section for naming rules.
;[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. 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. See [special characters|NAMING CONVENTION] section for naming rules.
At line 10 changed one line
;[Description]: The description field may be used to further define the purpose of the UserCalc in more detail than is available in the UserCalc name.
;[Description|DESCRIPTION]: The description field may be used to further define the purpose of the UserCalc in more detail than is available in the UserCalc name.
At line 12 changed one line
;[Product]: 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.
;[Product|PRODUCT]: 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.
At line 34 changed 3 lines
;[Compile]: This button allows the user to check the syntax of a UserCalc by creating the SQL code. 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.
;[Pre-Publish]: If the user is signed-on as 'P2K' then a UserCalc may be re-published directly in the IMUC form if it was already 'In Production' and needed to be re-validated. If a user has taken a copy of an 'In Production' UserCalc and wishes to test it without losing the original UserCalc, then they may publish it. This means that wherever the original UserCalc is referenced, Personality will now use the newly published version.
;[View]: [CLEANUP]
;[Compile|]: This button allows the user to check the syntax of a UserCalc by creating the SQL code. 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.
;[Pre-Publish|]: If the user is signed-on as 'P2K' then a UserCalc may be re-published directly in the IMUC form if it was already 'In Production' and needed to be re-validated. If a user has taken a copy of an 'In Production' UserCalc and wishes to test it without losing the original UserCalc, then they may publish it. This means that wherever the original UserCalc is referenced, Personality will now use the newly published version.
;[View|]: [CLEANUP]
At line 45 changed 2 lines
;CMD: See detailed descriptions in the [User Calc Commands|UC Commands] section.
;[OT|OPERANDn_TYPE]: OT is Operand Type. Operands must have a ‘Type’. This type is defined in the field before each Operand. See detailed descriptions in the [Operand Types|UC Operand Types] section.
;CMD: See detailed descriptions in the [User Calc Commands|UC COMMANDS] section.
;[OT|OPERANDn_TYPE]: OT is Operand Type. Operands must have a ‘Type’. This type is defined in the field before each Operand. See detailed descriptions in the [Operand Types|UC OPERAND TYPES] section.
At line 48 changed one line
;[OPER|OPERATORn]: Operators are the action to be taken in regard to the command issued and the operands indicated. See detailed description in the [Operators|UC Operators] section.
;[OPER|OPERATORn]: Operators are the action to be taken in regard to the command issued and the operands indicated. See detailed description in the [Operators|UC OPERATORS] section.
At line 56 changed one line
Data from the Variables tab is stored in [P2K_AM_USER_CALC_VARIABLES] table. Variables are used as temporary working storage to hold values required by the UserCalc. See the [User Calc Variables|UC Variables] Section.
Data from the Variables tab is stored in [P2K_AM_USER_CALC_VARIABLES] table. Variables are used as temporary working storage to hold values required by the UserCalc. See the [User Calc Variables|UC VARIABLES] Section.
This page (revision-41) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop