Work Order Check-in Management

This section explains how to record engineers’ on-site service activities, including work hours and location check-ins during fieldwork.

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

picture coming soon:

1. Check-in Scenarios

• Stores predefined scenario categories for engineer check-ins and calculates work hour types. Follow the product manual to create new scenarios; avoid adding custom fields.
• Click New under “Check-in Scenarios” to create a scenario (e.g., “Work,” “Business Trip,” or “Awaiting Materials”). Engineers can bind different scenarios to specific workflows during on-site operations.

picture coming soon:

2. Work Order Check-in Distance Validation

Purpose: Validates the engineer’s check-in location against the work order’s 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 in: Service Connector > System Settings > Fieldwork > Work Order Check-in.

picture coming soon:

• Enable distance validation for specific scenarios:
  • Edit a scenario, toggle “Enable Distance Validation,” and set the allowable deviation (maximum distance between check-in and service addresses).
  • Optionally allow check-in/check-out despite deviations.

picture coming soon:

• During check-in, the system automatically validates the engineer’s location against the service address.

picture coming soon:

• The Work Order Check-in Records object logs deviations if check-in/check-out is permitted despite validation failures.

picture coming soon:

3. Overlapping Check-in Validation

Ensures engineers cannot have overlapping check-ins for multiple work orders simultaneously.

• When enabled, engineers cannot start a new check-in until the previous one is completed.
• Set validation days to prevent forgotten check-outs (e.g., during holidays).

picture coming soon:
picture coming soon:

4. Location Capture Restrictions

Use cases: Track work hours without recording locations when unnecessary.

• Location Capture: Engineers within scope must provide precise location data for check-ins. Others can check in without location data.
• Scope: Apply to specific engineers or departments.
• Allow check-ins if location data cannot be retrieved due to network/system errors (records 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: Limits how far engineers can modify their check-in location.

picture coming soon:
picture coming soon:

6. International Maps

International locations use Google Maps, requiring a separate license purchase.

• Enable for engineers abroad to use Google Maps for location data.
• Scope: Restrict license usage to specific international engineers.

picture coming soon:

7. Photo Check-ins and Watermarks

• Watermark Settings: Apply watermarks (e.g., user name, timestamp) to check-in/check-out photos in the Work Order Check-in Records object (checkin_images and checkout_images fields).
• Scope: Company-wide by default. Engineers within scope will have watermarked photos. (Note: Include sub-departments when selecting scope.)

picture coming soon:
picture coming soon:

8. Check-in Modifications and Timeframe

Engineers may need to modify check-in records during service.

picture coming soon:

8.1 Modifications

• Enable modifications directly in standard workflows.
• Time Limit: Set how far back modifications are allowed (e.g., 3 days).
• Editable Fields: Time and address.

picture coming soon:

8.2 Modification Time Range

• Check-in Time Range: Restrict how much the original check-in time can be adjusted (e.g., ±1 hour).
• Check-out Time Range: Similarly limit check-out time adjustments.

picture coming soon:
picture coming soon:

• For completed check-outs, modify records via:
  • The Work Order Check-in Records object in the mobile app.
  • The Work Order detail page > Work Order Check-in Records related list.

picture coming soon:

9. Retroactive Check-ins

### 9.1 Retroactive Check-outs
> Use case: Engineers forget to check out after leaving a site.

• Enable multiple check-ins for unfinished workflows, allowing interim check-outs.
• Missing Check-outs: Unchecked-out records are marked as “Missing” at 23:59 and can be retroactively completed.
• Time Limit: Set how far back retroactive check-outs are allowed (e.g., 3 days).
• Editable Fields: Time and address.

picture coming soon:
picture coming soon:

• For completed check-outs, submit retroactive records via:
  • The Work Order Check-in Records object in the mobile app.
  • The Work Order detail page > Work Order Check-in Records related list.

picture coming soon:

9.2 Full-Day Retroactive Check-ins

Use case: Engineers forget to check in for an entire day of fieldwork.

1. Required Fields for Submission:

picture coming soon:
picture coming soon:

1. Role Permissions: Grant submission rights to specific roles (e.g., Service Connector admins/dispatchers).

picture coming soon:

1. Submit via the Work Order Check-in Records list in Web or mobile.

picture coming soon:

1. Auto-Filled Fields:
   • Check-in time/address = Submitted retroactive values.
   • Check-out time/address = Submitted retroactive values.
   • Type = “Full-Day Retroactive.”

10. Syncing Work Order Check-ins to Fieldwork

Syncs work order check-ins with general fieldwork records for unified reporting.

• Sync Fieldwork Records: Enable to sync data in real time.

picture coming soon:

Note: If Advanced Fieldwork is enabled, ensure all engineers have “Fieldwork Check-in” as an allowed type in their rules.

picture coming soon: