DOCSEARCHbyAlgolia
Submit Docs

mtime Updates

website·Indexed 30 days ago

https://knc.mtime.app

Release notes and update logs for mtime, including details on Version 5.22 and Version 5.23, featuring improvements such as dynamic approval and absence management.

Tokens
1.1K
Snippets
3
Records
22
Agent score
47%

What's inside mtime

  1. Integrate with Timegrip and Visma Løn

    Version 5.22 introduces integrations for:

    • Timegrip: Supports importing registrations, including those that span across midnight.
    • Visma Løn: New integration for payroll processing.

  2. Manage dynamic approval flows

    A new dynamic approval feature allows for flexible configuration of approval workflows. Tables now update correctly immediately after new dynamic approvers are added.

  3. Manage absence requests and secondary codes

    Absence requests are now visible in the registration schedule and summary. The system supports absences with secondary absence codes and prevents absence requests that exceed the norm hours.

  4. Integrate with Timegrip and Visma Løn

    Version 5.22 introduces native integrations for importing data and managing payroll:

    • Timegrip: Supports importing registrations, including those that span across midnight.
    • Visma Løn: New integration available for payroll processing.

  5. Manage absence requests and validation

    Version 5.23 introduces several updates to absence management:

    • Absence requests are now visible in the registration schedule and summary.
    • Support for absences with secondary absence codes is available.
    • The system now prevents absence requests that exceed the norm hours.

  6. Configure dynamic approval flows

    The dynamic approval feature allows for flexible setup of approval workflows. When new dynamic approvers are added, the associated tables update automatically to reflect these changes.

  7. Configure time terminal scan threshold

    Use the ConsiderScanAsConnectedThresholdHours configuration key to set the threshold for when a time terminal scan is considered connected.
    // Example configuration key
ConsiderScanAsConnectedThresholdHours: [value]

  9. Configure time terminal scan threshold

    Use the ConsiderScanAsConnectedThresholdHours configuration key to set the threshold for when a time terminal scan is considered connected.
    ConsiderScanAsConnectedThresholdHours: [value]

  11. Exclude records from the 48-hour rule

    The ExcludeFrom48HoursRule parameter can be used to prevent specific records or settings from being subject to the 48-hour validation rule.
    ExcludeFrom48HoursRule: true

  12. Exclude inconveniences based on reason code

    A new option CheckExcludeInconvenienceOnReasoncode allows users to exclude inconveniences based on a specific reason code during inconvenience calculation.