Timesheet Management System (TMS)

Features added to Timesheet Management System

The following features have been added to Timesheet Management System (TMS) for the 25.May Release:

Time Card Status

This feature introduces a Daily Time Entry Status system in Zenople by Aqore, allowing users to easily identify and manage the state of each daily time entry. Statuses are determined automatically based on shift times and user actions, streamlining daily updates and supporting compliance.

Example Scenario 1: No Shift

Example Scenario 2: Before Shift Starts (Shift Time: 9 AM to 6 PM, Current Time: 8:50 AM)

Example Scenario 3: During Shift Time (Shift Time 9:00 AM to 6:00 PM, Current Time 9:10 AM)

Example Scenario 4: After shift ends (Shift Time 9:00 AM to 6:00 PM)(Current Time: 6:10 PM)

Real-Time Synchronization between Timeclock and Timesheet

This feature enhances the time tracking functionality in Zenople by Aqore by implementing real-time synchronization between Timeclock and Timesheet. This ensures that any updates made in either system are immediately reflected in the other, preventing duplicate or conflicting entries across multiple navigations.

Functionality

• Bidirectional Sync: Time entries updated on the Timesheet will be instantly available in Timeclock and vice versa.
• Comprehensive Data Sync: The synchronization includes:
  • Hours
  • Breaks
  • Timesheet, Timeclock data
  • Work Board, Timeclock data
• Multi-Platform Sync: Synchronization occurs across various platforms:
  • Employee Portal
  • Customer Portal
  • Timeclock systems
• Admin Summary Integration: Synchronized data is reflected in the Admin Summary.

Enhanced Exception Handling in Work Board: "Run Exceptions".

This update to the Zenople Work Board improves the workflow for handling exceptions when managing transaction batches. Users can now flexibly filter, approve, and re-run exceptions directly from the Work Board, streamlining the exception resolution and batch closure process.

Functional Changes

• Flexible Exception Filtering:
   When using the "View Batches" feature and performing "Close Batch" or "Run Exception" actions, users are no longer restricted to a predefined exception filter. Users can filter and select any exception(s) for review and action.
• Action Logic Based on Selection:
  • If the user selects only one exception, they are presented with an "Approve and Next"action (instead of "Close Batch").
    • This allows the user to approve the selected transaction(s) for that exception.
    • After approval, exceptions are re-run automatically.
    • If new or remaining exceptions are found, the process repeats, guiding the user through each unresolved exception.
    • If no further exceptions are found, a confirmation dialog is shown and the batch can be closed.
  • If the user selects all exceptions, they are able to proceed to close the batch after confirming all exceptions are resolved.
  • When the user selects all exceptions and selects filter, the Close Batch action is shown.
  • If the user selects only some of the transactions and clicks Approve and Close, it approves the exceptions for the selected ones but returns to the Exception window, ensuring that the remaining transactions in the batch are not missed.
  • All exceptions for all selected transactions shown in the filtered view must be approved in order to close the batch.
  • The same behavior applies to the Workboard grid.

New Transaction Source for Timeclock Application Data

This feature introduces a dedicated transaction source to distinguish data originating from the Timeclock application-specifically including offline and online punches via Zentime-from other sources. The system will now clearly identify and manage transactions created from Timeclock, enhancing traceability, batch management, and user experience consistency across platforms.

Automated Daily Transaction Creation via Midnight Job

This feature introduces a daily midnight job in Zenople that automatically creates transactions, replicating the manual "Create Transaction" action in TMS. It ensures consistency by following the same validation rules, exception handling, and workflows, and adheres to Transaction Week settings from the Customer Service Profile. The job targets the current Accounting Period, even if it is in a "To Be Open" state. Transactions are created for assignments and assignment schedules where the End Reason has the "Create Transaction" property enabled. This feature ensures efficient, error-resistant transaction creation, reduces manual intervention, and maintains alignment with existing TMS workflows and compliance rules.