Edit and apply actions to timelogs
Actions that can be performed on individual and a group of timelogs.
Using timelog actions and other settings, you can modify existing timelogs as well as add or remove information. This guide features a complete list of all the available timelog actions. Next, some additional settings such as time and mileage and lunch and break policies are discussed. Lastly, you learn about the bulk action types that are available if multiple timelogs are selected.
Timelog actions
You can access timelog actions by selecting the more icon on an individual timelog in the timelogs list, as shown in the following screenshot.
![Timelog actions](https://files.readme.io/471898c-image.png)
Timelog actions
PERMISSIONS
You may perform actions on a timelog if you have the Update Timelog permission enabled for your role in Web App > Administration > Role Permissions > Timelogs.
This permission doesn't apply to actions that have their own distinct permission setting. Such cases are described further in this document.
The following actions are available.
Set Regular Time
Using this action, you can set a manual punch from 12 AM to 23:59 PM. The action is not be available in the following cases:
- The timelog has a missed punch.
- The timelog is pending, which means that the employee has punched in but hasn’t punched out yet.
- The current selected day is a holiday. In this case, the option is replaced with the Set Holiday Work Time option if it's activated from administration settings.
Set Fast 8
This action is a quick way to add an 8-hour-long entry to the timelog. The system creates an entry from 7 AM to 3 PM, which you are able to edit afterwards. The option is not be available in the following cases:
- The timelog already contains a punch out time between 12 AM and 3:59 PM.
- The timelog has both punch in and punch out times already.
- The timelog has a Leave Request.
- Holiday 8h has been applied already.
Holiday actions
Holidays are specified under Administration > Holidays > Calendar. In Administration > Holidays > Policies, you can apply the following setting.s for salary and hourly employees:
- Auto-apply Holiday Policy. If activated, the system automatically applies an 8-hour timelog entry for all the empty timelogs on a holiday and generates a [HOL] pay ID. If the setting is not activated, you can perform the same action manually, using the Set Holiday Leave action on a timelog.
- Apply Holiday Work Policy. If activated, the setting accounts for cases when an employee has worked on a holiday. Such cases fall under the [HOL_WORK] pay ID. The entry is marked as holiday work automatically if the employee makes a punch on that day, and it's also possible to add an entry manually using the Set Holiday Work Time timelog action.
NOTE
If you mark a date as a holiday, the existing timelog entries for that date are not converted to [HOL_WORK] automatically . You need to use the Set Holiday Work Time action on those timelogs to appply holiday work manually.
Change Job Site
Using this action, you can change the timelog's job site and transfer all the timelog entries to another job site. When you make the change, the timelog will be removed from the current job site's list of timelogs and will appear under the new job site.
PERMISSIONS
You may change the job site of a timelog if you have the Change job site permission enabled for your role in Web App > Administration > Role Permissions > Timelogs.
Split Timelog
PERMISSIONS
You may perform the Split Timelog action if you have the Split Timelog permission enabled for your role in Web App > Administration => Role Permissions => Timelogs.
The Split Timelog action helps you address the situation when an employee has worked at more than one job site during the day but has punched in and out at one job site only. Splitting the timelog breaks down the entry between two or more job sites. The action opens a sidebar where you can add one or more Split Job Sites on top of the Main Job Site and distribute the timelog's working hours among them. During the distribution process, you see how many hours remain and are notified when you exceed the recorded timelog hours.
NOTE
When splitting a timelog, the total sum of hours from each job site should be equal to the initial timelog entry duration. In addition, you may not assign 0 hours to the Main Job Site.
The following screenshot shows the timelog splitting dialog box.
![Splitting a timelog](https://files.readme.io/7338f4f-image.png)
Splitting a timelog
There are some differences when splitting a timelog for an hourly and salary employee. The following sections discuss each case in greater detail.
Salary timelog split
The Split Timelog action is available for salary timelogs if the timelog has one or more entries without a leave request. The option is available even if there's a missed punch (for example, the employee has punched in but hasn't punched out), since a default 8-hour entry is applied to a salary timelog if there is at least one punch.
Hourly timelog split
Similar to salary timelogs, for hourly timelogs, the Split Timelog action is available if the timelog has one or more entries without a leave request. However, there are certain cases when the timelog meets the above condition but can't be split:
- If any of the timelog entries has a missed punch.
- One of the timelog entries is already split.
- The timelog is cost coded.
Swap Timelog
Using the swap option, you can swap the timelog's punch in and punch out times. The option becomes available on a timelog entry if the entry contains only a punch in time or only a punch out time. This can occur when, for example, an employee has punched out instead of punching in when entering the job site through the Kiosk App.
PERMISSIONS
You may perform the Swap Timelog action if you have the Swap timelog entries permission enabled for your role in Administration > Role Permissions > Timelogs.
The following GIF illustrates the process of swapping a timelog.
![Swapping a timelog](https://files.readme.io/a5fbab8-Screen_Recording_2023-08-11_at_10.41.43.gif)
Swapping a timelog
Remove Punch In
Using this action, you can remove a punch in registered earlier. The action is not available for leave request entries and if the punch time of the entry is missing.
Remove Punch Out
Using this action, you can remove a punch out registered earlier. The action is not available for leave request entries and if the punch out time of the entry is missing.
Delete Entry
Using this action, you can delete an entry from a timelog.
NOTE
In case of split timelogs, deleting an entry from any of the split timelogs removes the associated entries from the rest of the split timelogs as well.
Delete Timelog
This action deletes a timelog from the job site. It is available if the timelog doesn't contain any entries.
Leave Request
Leave request indicate reasons for employee absence to allow for accurate reporting and employee tracking. Leave request types are configured under Administration > Settings > Pay IDs > Leave Pay IDs and can be set to be applicable for any or both of the pay groups (hourly and salary). When adding a leave request, you also have the option to specify a duration in hours (an integer from 1 to 8).
![adding a leave request to a timelog](https://files.readme.io/338a9de-Screen_Recording_2023-08-03_at_19.44.23.gif)
Adding a leave request to a timelog
Lunch and break policies
Each timelog in the timelogs list can contain Lunch Policy and Break Policy toggles.
NOTE
Lunch and Break policies are applicable to hourly employees only.
![lunch and break policy toggles on the timelog row](https://files.readme.io/90c29ac-image.png)
Lunch and Break Policy toggles
If Lunch Policy or Break Policy auto-apply is enabled for the employee (it needs to be enabled for both the employee and job site to be applied on the timelog), the corresponding timelog toggle will be switched on automatically as soon as a punch entry is added to the timelog. In addition, lunch or break duration will be automatically subtracted from the timelog entry. You can then change these settings manually if needed.
PERMISSIONS
You may switch Lunch and Break Polcies if you have the Enable/disable lunch/break policy permission enabled for your role in Administration > Role Permissions > Timelogs.
![switching on and off lunch and break policy toggles on a timelogs, which in turn affects the recorder hours](https://files.readme.io/0b145aa-Screen_Recording_2023-08-07_at_15.58.06.gif)
Enabling/disabling Lunch and Break Policy on a timelog
Bulk actions
When you select more than one timelog, a menu with bulk actions appears above the timelogs list. Here, you can perform actions similar to those that are available for individual timelogs.
![Bulk actions](https://files.readme.io/bd8fc3b-Screen_Recording_2023-08-10_at_20.13.00.gif)
Bulk actions
A bulk action is active (can be performed) for the selected timelogs if all the timelogs meet the preconditions for that action. The following table lists all the available bulk actions and their corresponding preconditions.
Action | Timelog preconditions |
---|---|
All actions | Selected timelogs need to belong to the same job site and be added on the same day. |
Lunch Policy toggle | All the timelogs are by hourly employees and contain at least one entry. |
Break Policy toggle | All the timelogs are by hourly employees and contain at least one entry. |
Set Fast 8h | None of the timelogs has an entry, and none of the timelogs is split. |
Leave Request | None of the timelogs is split, and all the selected timelog employees are either all hourly employees or all salary employees. |
Change job site | None of the timelogs is split, and none of the timelogs has a leave request. Moreover, all the selected timelogs need to contain one entry only. |
Set Punch In Time | None of the timelogs has more than one entry. |
Set Punch Out Time | None of the timelogs has more than one entry. |
Resolve flags | At least one timelog is flagged. |
Even if a bulk action meets the precondition listed above and is active, there can be additional limitations, which you'll learn about through error messages that are displayed when applying an action.
Updated 3 months ago