Work Order Clock-in Management

This section describes how to record engineers’ on-site service activities, including clock-in/clock-out logs and working hours during fieldwork.

Access Path: Service Connector > System Settings > Work Order Clock-in

picture coming soon:

1. Clock-in Scenarios

• Stores predefined clock-in scenario classifications and working hour calculation types for engineers. Follow the product manual to create new scenarios; custom fields are not recommended.
• Click New under “Clock-in Scenarios” to create a Work Order clock-in scenario. Name scenarios based on working hour categories (e.g., Work, Business Trip, Awaiting Materials). Engineers can bind different scenarios to specific processes during on-site operations.

picture coming soon:

2. Work Order Clock-in Distance Validation

Purpose: Validates the distance between an engineer’s clock-in location and the Work Order service address to prevent fraudulent check-ins and ensure on-site presence.

• By default, the system validates against the “Service Address” field in the Work Order object. Adjust this setting at: Service Connector > System Settings > Fieldwork > Work Order Clock-in.

picture coming soon:

• Enable distance validation for specific clock-in scenarios by editing the scenario and setting an allowable deviation range (maximum distance between clock-in and service addresses).
• Optionally allow clock-in/clock-out outside the deviation range.

picture coming soon:

• The system automatically validates locations during clock-in.

picture coming soon:

• Exceptions and deviation distances are logged in the Work Order Clock-in Logs object if validation is enabled but overridden.

picture coming soon:

3. Overlapping Clock-in Validation

Purpose: Ensures engineers cannot clock in for multiple Work Orders simultaneously or have overlapping clock-in records.

• When enabled, engineers cannot start a new clock-in until the previous one is completed.
• Validation Period: Set the maximum lookback period (e.g., 3 days) to prevent forgotten clock-outs during holidays.

picture coming soon:
picture coming soon:

4. Location Capture Restrictions

Use Case: Track engineers’ working time without recording locations when unnecessary.

• Location Capture: Engineers within the applicable scope must provide precise location data for clock-in. Others can clock in without location.
• Scope: Apply to specific engineers or Depts.
• Allow clock-in without location data if network/system errors occur (logs will lack address data).

picture coming soon:

5. Location Adjustment Range

• Engineers can manually adjust inaccurate system-captured locations within a predefined range.
• Adjustment Range: Defines the maximum allowable deviation for manual adjustments.

picture coming soon:
picture coming soon:

6. International Maps

Note: Google Maps is used for international location services, requiring a separate license.

• Enable for engineers abroad to use Google Maps for clock-in.
• Scope: Restrict license usage to specific international engineers.

picture coming soon:

7. Photo Clock-in and Watermarks

• Watermark Settings: Apply watermarks (e.g., user name, timestamp) to check-in (checkin_images) and check-out (checkout_images) photos in the Work Order Clock-in Logs object.
• Scope: Defaults to company-wide. Ensure subordinate Depts. are included when customizing.

picture coming soon:
picture coming soon:

8. Clock-in Record Adjustments

Use Case: Engineers may need to modify clock-in records post-service.

picture coming soon:

8.1 Adjustments

• Enable/disable adjustments per standard workflow.
• Adjustment Window: Set a time limit (e.g., 3 days) for modifying records.
• Adjustable Fields: Time and/or address.

picture coming soon:

8.2 Time Adjustment Range

• Check-in Time Range: Restrict adjustments to ±1 hour of the original time (e.g., 8:00–10:00 for a 9:00 check-in).
• Check-out Time Range: Similarly limit adjustments (e.g., 17:00–19:00 for an 18:00 check-out).

picture coming soon:
picture coming soon:

• For completed Work Orders, adjust records via the Work Order Clock-in Logs object in mobile or the Work Order detail page.

picture coming soon:

9. Retroactive Clock-in

### 9.1 Retroactive Check-out
Use Case: Engineers forget to check out after a service day.

• Enable multiple clock-ins per workflow to allow interim check-outs.
• Missing Check-out: Unchecked records are marked as “Missing” at 23:59 and can be retroactively completed.
• Retroactive Window: Set a time limit (e.g., 3 days) for submissions.
• Adjustable Fields: Time and/or address.

picture coming soon:
picture coming soon:

• Submit retroactive check-outs via the Work Order Clock-in Logs object.

picture coming soon:

9.2 Full-Day Retroactive Clock-in

Use Case: Engineers forget to clock in for an entire service day.

1. Required Fields:
   picture coming soon:
   picture coming soon:

2. Permission Assignment: Grant submission rights to Roles like Service Connector Admins or Dispatchers.
   picture coming soon:

3. Submit via the Work Order Clock-in Logs object in Web or mobile.
   picture coming soon:

4. Auto-Filled Fields:

   • Check-in time/address = Retroactive check-in time/address
   • Check-out time/address = Retroactive check-out time/address
   • Type = Full-Day Retroactive

10. Sync Work Order Clock-in to Fieldwork

Purpose: Combine Work Order clock-in data with non-Work Order fieldwork records for unified analysis.

• Enable real-time syncing to standard fieldwork.

picture coming soon:

Note: If Advanced Fieldwork is enabled, ensure all engineers’ rules include the “Fieldwork Check-in” type.

picture coming soon: