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 3 removed one line
[{Image src='IMUC.JPG' width='360' align='right' link='attach/IMUC/IMUC.JPG'}]
At line 5 changed 2 lines
UserCalcs may be defined within the Define UserCalcs (IMUC) form. This screen will allow
you to create the lines, variables, commands, etc. for each UserCalc. The definition data for the Define User Calculations screen is stored in the [P2K_AM_USER_CALCS] tables.
UserCalcs may be defined within the Define UserCalcs (IMUC) form. This screen will allow you to create the lines, variables, commands, etc. for each UserCalc. The definition data for the Define User Calculations screen is stored in the [P2K_AM_USER_CALCS] tables.
At line 12 changed one line
;[Product|PRODUCT_CODE]: 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.\\ \\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.
;[Product|PRODUCT_CODE]: 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.\\ \\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.\\ \\NOTE In the NG system (5.01+), the PRODUCT field can not be changed once it has been added. This was done to avoid issues/errors arising from building a user calc for one product and then changing it to another.
At line 30 changed one line
|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.
|Secondary WF |This option tells the Workflow 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.
At line 31 added 2 lines
;[WF Firing Sequence|USER_CALC_SEQUENCE]: not used by the system;
At line 34 changed one line
;[Pre-Publish|ACT_PUBLISH_UC_IMUC]: When the UserCalc has been Compiled, the UserCalc may be 'pre-published'. This will change the status from 'Under Construction' to 'To Be Published'. Once in this status, the UserCalc may be officially published in [IMUCA]. \\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, [{$applicationname}] will now use the newly published version.
;[Pre-Publish|ACT_PUBLISH_UC_IMUC]: When the UserCalc has been Compiled, the UserCalc may be 'pre-published'. This will change the status from 'Under Construction' to 'To Be Published'. Once in this status, the UserCalc may be officially published in [IMUCA]. \\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.
At line 41 changed one line
;[Line|COMMAND_LINE]: This field defines the sequential order in which the UserCalcs will follow instructions. (00010, 00020, etc.)
;[Line|USER_CALC_LINE]: This field defines the sequential order in which the UserCalcs will follow instructions. (00010, 00020, etc.)
At line 64 changed one line
;[Description]: To make UserCalcs more easily read and maintained, a Notes field has been provided. Notes should be used to explain the calculations made and the logic of the UserCalc. If the user calc is used for workflow emails, the text of the email body is added here.
;[Description]: To make UserCalcs more easily read and maintained, a Notes field has been provided. Notes should be used to explain the calculations made and the logic of the UserCalc. If the user calc is used for workflow emails, the text of the email body is added here. The text used in the description should not use ORACLE RESERVED words or special characters.
At line 95 removed one line
At line 97 added one line
%%warning
At line 99 added one line
please note that user calculations are limited to 30,000 bytes. If you have a usercalc that exceeds this volume it is recommended to use the "CALL" program to reduce the size, or to break the usercalculation into smaller logical components.
At line 101 added 4 lines
Bytes will also include logic called in the "Notes" section of the user calculation.%%
This page (revision-41) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop