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

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

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
17 26-Nov-2021 10:22 7 KB kparrott to previous
16 26-Nov-2021 10:22 7 KB JEscott to previous | to last
15 26-Nov-2021 10:22 7 KB JEscott to previous | to last
14 26-Nov-2021 10:22 7 KB JEscott to previous | to last
13 26-Nov-2021 10:22 6 KB JEscott to previous | to last
12 26-Nov-2021 10:22 6 KB JEscott to previous | to last
11 26-Nov-2021 10:22 6 KB JEscott to previous | to last
10 26-Nov-2021 10:22 6 KB JEscott to previous | to last
9 26-Nov-2021 10:22 6 KB JEscott to previous | to last
8 26-Nov-2021 10:22 6 KB JEscott to previous | to last
7 26-Nov-2021 10:22 5 KB JEscott to previous | to last
6 26-Nov-2021 10:22 5 KB JEscott to previous | to last
5 26-Nov-2021 10:22 4 KB JEscott to previous | to last
4 26-Nov-2021 10:22 4 KB JEscott to previous | to last
3 26-Nov-2021 10:22 4 KB JEscott to previous | to last
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 4 KB JEscott to last

Page References

Incoming links Outgoing links
CASCADE AND LEAVE REASONS
CASCADE AND LEAVE REASONS

Version management

Difference between version and

At line 10 changed 2 lines
*The lexicon [X_LEAVE_REASON] has been modified to include the new leave reason <<Required>>.
*Leave verification routines have updated to populate the leave line leave reason value to <<Required>> when the leave policy requires a leave line.
*Workflow can also be created to populate the leave reason.
----
At line 26 changed one line
 To make the leave reason a requirement the Leave Reason Req’d Toggle must be checked in IALP.
To make the leave reason a requirement the Leave Reason Req’d Toggle must be checked in [IALP].
At line 33 removed one line
*You will not be able to delete/remove leave lines from [IAAL].
At line 36 added one line
At line 37 changed 3 lines
*Since the leave line is created on the fly the leave reason can only be filled by selecting the ‘Show Leave Reason Require’ button ([ACT_SHOW_LEAVE_REASON_REQUIRED]). This button is available in the header of [IPTS].
Note: The [ACT_SHOW_LEAVE_REASON_REQUIRED] button may be added on any timesheet screen or leave entry screen similar to the way it displays in [IPTS].
*When the user clicks on this button a window displays with the leave entries that require a leave reason. The user may then fill the leave reason. The user may also enter a Leave Reason free form description in the ‘Leave Reason Text’ field. If the window is blank there are no leave reasons to fill.
*After saving the records, an indicator will display in the Value field. If the record is not in focus, the indicator may be a red disc marked with a white ‘x’ in the center, this indicates a leave reason is required. When the mouse is hovered over the icon a bubble text will appear with a message indicating the leave reason is required. If the record is in focus, the value will be crossed out, the red disc icon will not display. If the indicator is a yellow triangle marked with a white ‘!’ in center, this indicates the leave has cascaded. Again, the user may hover their mouse over the icon to display the message.
*Since the leave line is created on the fly the leave reason can only be filled by selecting the [Show Require Leave Reason| ACT_SHOW_LEAVE_REASON_REQUIRED] button. This button is available in the header of [IPTS]. Note: The [Show Require Leave Reason|ACT_SHOW_LEAVE_REASON_REQUIRED] button may be added on any timesheet screen or leave entry screen similar to the way it displays in [IPTS].
*When the user clicks on this button a window displays with the leave entries that require a leave reason. The user may then fill the leave reason. The user may also enter a Leave Reason free form description in the ‘Leave Reason Text’ field. If the window is blank there are no leave reasons to fill.
At line 41 changed 3 lines
*Enter the leave lines and save the records.
*After saving the records, click the ‘Show Require Leave Reason’ button.
*Select the Leave Reason as required.
!IPTR / IPTRE – Entering Leaves and Leave Reasons
At line 45 added 8 lines
*Leaves may be entered directly as a pay transaction in the grid of [IPTR] and [IPTRE].
*After saving the records, if the leave requires a leave reason or if the leave has cascaded an indicator will display in the Value field. If the record is not in focus, the indicator may be a red disc marked with a white ‘x’ in the center, this indicates a leave reason is required. When the mouse is hovered over the icon a bubble text will appear with a message indicating the leave reason is required. If the record is in focus the value will be crossed out and double arrows will display which may be clicked to reveal the leave dialog. If the indicator is a yellow triangle marked with a white ‘!’ in center, this indicates the leave has cascaded. Again, the user may hover their mouse over the icon to display the message.
*The transactions within the grid may be filtered to only display those requiring a leave reason or to display leaves which have cascaded. This may be done via the Filter By drop down just beneath the grid.
*The Leave Reason may be provided in the Leave Information section within the Time Codes tab of [IPTR] / [IPTRE].
!IPPH – Entering Leaves and Leave Reasons
* Leaves may be entered directly as a pay line in [IPPH].
* After saving the records, if the leave requires a leave reason or if the leave has cascaded an indicator will display in the Value field. If the record is not in focus, the indicator may be a red disc marked with a white ‘x’ in the center, this indicates a leave reason is required. When the mouse is hovered over the icon a bubble text will appear with a message indicating the leave reason is required. If the record is in focus, the value will be crossed out, the red disc icon will not display. If the indicator is a yellow triangle marked with a white ‘!’ in center, this indicates the leave has cascaded. Again, the user may hover their mouse over the icon to display the message.
*The Leave Reason field has been added to [IPPH]. The field may be found in the Line Info tab of the Pay Lines Tab.
At line 49 removed one line
*Leave reasons will not display in [IPPH].
At line 58 added 5 lines
----
!!IMUC and IMWA – User Calcs and Workflows (optional)
*Leaves may be updated directly by the use of a workflow user calc.
*Below is an example of a simple workflow for this purpose
**Example 1: The user calc workflow below will update the leave reason to vacation when the selected time code is vacation. This means, when a user enters a leave transaction in [IPTR] and saves the record the Reason field in the Time Code tab will be updated to Vacation automatically. Other time codes can be added to this user calc based on the clients need. This user calc would not create a workflow action such as a message or email since no setup was defined in [IMWA].
At line 66 added one line
[{Image src='WF_Leave_Reason.JPG' width='650'}]
At line 57 removed one line
[{If var='loginstatus' contains 'authenticated'
At line 59 removed 3 lines
----
![Discussion|Edit:Internal.CASCADE AND LEAVE REASONS]
[{InsertPage page='Internal.CASCADE AND LEAVE REASONS' default='Click to create a new discussion page'}]
At line 63 changed one line
}]
----
![Notes|Edit:Internal.CASCADE AND LEAVE REASONS]
[{InsertPage page='Internal.CASCADE AND LEAVE REASONS' default='Click to create a new notes page'}]
This page (revision-17) was last changed on 26-Nov-2021 10:22 by kparrottTop