This page (revision-3) was last changed on 05-Dec-2022 14:48 by Kevin Higgs

This page was created on 05-Dec-2022 14:40 by Kevin Higgs

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
3 05-Dec-2022 14:48 2 KB Kevin Higgs to previous
2 05-Dec-2022 14:43 2 KB Kevin Higgs to previous | to last
1 05-Dec-2022 14:40 2 KB Kevin Higgs to last

Page References

Incoming links Outgoing links
DISBURSEMENT_MESSAGE
DISBURSEMENT_MESSAGE

Version management

Difference between version and

At line 1 added one line
At line 2 changed 3 lines
Personality allows users to create an automatic check message(s) through the creation of a [UserCalc|USERCALC] processed by [UPDISB].
\\ \\
The automatic check message can be at the employee level using qualifications in the [UserCalc|USERCALC].
Personality allows users to create an automatic check message(s) through the creation of a [UserCalc|USERCALC] processed by [UPDISB]. The automatic check message can be at the employee level using qualifications in the [UserCalc|USERCALC].
At line 7 changed one line
\\ \\
\\
At line 9 changed one line
\\ \\
\\
At line 11 removed 4 lines
\\ \\
If the message is for all employees, then set up a “User Variable” of type CHAR, and "RETURN' this User Variable from the Disbursement User Calc.
\\ \\
If you define the message directly on the usercalc varible tab, you will have to go into the User Variable before each pay and reset the message.
At line 16 changed one line
For this reason, it is recommended that you instead set up your message in IMVR to allow date effective changes or updates without having to unpublish a usercalc.
If the message is for all employees, then set up a “User Variable” of type CHAR, and "RETURN' this User Variable from the Disbursement User Calc. You will have to go into the User Variable before each pay and reset the message or key in multiple user variable details with the proper effective date (based on pay issue date).
At line 18 changed one line
If the message is employee specific, then the value returned would have to be a CHAR value derived logically through the ‘Alphanumeric’ operand types or a User Variable from within the usercalc.
If the message is employee specific, then the value returned would have to be a CHAR value derived logically through the ‘Alphanumeric’ operand types or a User Variable.
This page (revision-3) was last changed on 05-Dec-2022 14:48 by Kevin HiggsTop