Field Standard Operating Procedure (SOP) Template

Work Order On‑Site Standard Operating Procedure (SOP) defines standardized on‑site steps. It supports following steps in sequence or executing steps flexibly so engineers can complete on‑site work efficiently while recording their labor time.

Usage example:

Operation entry: Service Connector -> System Settings -> On‑site Standard Operating Procedure

picture coming soon:

1. SOP Templates

1. Click [New] to create a new SOP template

picture coming soon:

1. Fill in the SOP template basic information

• Name: SOP name
• Description: notes about the SOP purpose, etc.
• Type: who uses this SOP — internal company use or Service Provider use
• Applicable scope: define the SOP’s applicable scope (used when matching SOPs in the workflow “SOP” node by rules; for the same Work Order Record Type there can be multiple SOPs and this allows rule‑based selection)

Then choose the SOP task/step layout

picture coming soon:

2. SOP Steps (Processes)

Step (Process): If the on‑site Work Order tasks contain many steps, split them into multiple processes, e.g., preparation, repair task, result check.

Multi‑process scenario: click “+” to add a process. If single‑process is selected, there’s no add button. Click the process panel to enter process name and description. Click Delete on the process to remove it.

picture coming soon:

3. Actions

Action: what to do. Click “Add Action” to add an action item to a process. Click “Node Settings” on the right to enter action name and description. Multiple action types are supported.

Action modes:

(1) Single action: done once per SOP instance, e.g., confirm device Fault.

(2) Repeating action: allowed to repeat on a set frequency. For example, after SOP start do it every day or every sign‑in until SOP completes (e.g., daily check).

picture coming soon:

3.1 Single Action

3.1.1 Single action types

• Edit record:
  • (1) Edit Work Order fields such as location, description, or edit fields on objects related to the Work Order (for example edit the Device object’s “latest address” field).
  • (2) Flow edit: you can edit master‑and‑Sub‑object together, e.g., update Device and associated Fault.

picture coming soon:

• Select or create related record:
  • (1) Select an existing related record and link it to the Work Order.
  • (2) If you check “Allow only create, not link to existing,” users can only create a new related record (for example, create a Device operation record).

picture coming soon:

picture coming soon:

• Bulk create related records: create multiple related object records for the Work Order in batch (for example bulk create Part Consumption records).

picture coming soon:

• Add inspection group: you can add an inspection group (see Inspection Groups and Checklist Templates). You can either select a fixed inspection group or match an inspection group by rule.

picture coming soon:

• Generate service report: add an action to generate a service report. The engineer must complete all required actions before generating the service report. See Service Report Templates.

Note: Generating a service report currently does not support “completion condition” validation nor “post‑completion actions.”

picture coming soon:

picture coming soon:

• Generate service evaluation QR code: adding an evaluation QR code action aggregates all engineer actions into a single node.

Note: Evaluation templates are not matched by Work Order conditions (Record Type); only fixed service evaluation templates are supported here. If you need rule‑based matching for evaluation templates, configure a separate User Evaluation node.

picture coming soon:

picture coming soon:

3.1.2 Single action execution prompts

1. Action execution prompts: add guidance or step‑by‑step instructions to an action so engineers see operational tips while working, improving efficiency.

picture coming soon:

picture coming soon:

3.1.3 Single action assignee

Action assignee: Click Edit to choose the assignee. Default is Work Order.Engineer. Currently only two personnel fields are supported: Engineer (field_xcfwry__c) and Related_Service_Personnel (related_service_personnel__c).

picture coming soon:

3.1.4 Single action settings

Action settings:

• Required: validate this action is completed when clicking process “Complete and Sign‑out” or when clicking the SOP action “Complete.”
• Preceding action: cannot execute this action until the specified preceding action(s) are complete. Only actions within the same process are supported.
• Show “Skip this step” button: when current action is incomplete show a “Skip this step” button to proceed to the next action.
• Auto advance: after an engineer completes an action, the interface can automatically move to the next action. (This interaction is supported in the mobile app only.)
• Completion condition: click Edit to add a validation function for completing this action.
• Post‑completion action: click Edit to add a function that runs automatically after action completion.

picture coming soon:

Front‑end operation example:

picture coming soon:

3.2 Repeating Actions

Repeating action: allowed to repeat and set a frequency. For example, require that from SOP start the action runs every day or every sign‑in until SOP completes (e.g., daily inspection).

3.2.1 Repeating action types

• Create related record: create related object records, e.g., create a Device operation record.

picture coming soon:

• Add inspection group

• You can add an inspection group (see Inspection Groups and Checklist Templates).
• You can either select a fixed inspection group or match it by rule.

picture coming soon:

3.2.2 Repeating action prompts

1. Action execution prompts: add guidance or steps to the action item to guide engineers and improve efficiency.

picture coming soon:

3.2.3 Repeating action assignee

Action assignee: Click Edit to choose the assignee. Default is Work Order.Engineer. Currently supported personnel fields: Engineer (field_xcfwry__c) and Related_Service_Personnel (related_service_personnel__c).

Note: If a repeating action’s assignee is set to Related_Service_Personnel and the Work Order has multiple Related_Service_Personnel, the system currently supports counting actions by action frequency only. For example, a “daily” frequency generates one daily action overall — it does not create one action per Related_Service_Personnel.

picture coming soon:

picture coming soon:

3.2.4 Repeating action frequency

• Unlimited repeats: no limit (after an action completes, the system waits 5 minutes then creates a new pending action). Cannot set as Required.
• Once per day: one per day (system generates a pending action automatically at 00:00 each day) until the entire SOP node is completed. If marked Required, the whole SOP completion will validate required items.
• Once per sign‑in: requires enabling process sign‑in with repeat sign‑in. Each time the engineer signs into the process it generates a pending action until the process is completed. If marked Required, validation occurs at sign‑out or process complete and sign‑out.

picture coming soon:

3.2.5 Repeating action settings

Action settings:

• Required: validate this action is completed when clicking process “Complete and Sign‑out” or when clicking SOP action “Complete.” (Actions with unlimited repeats cannot be set Required.)
• Completion condition: click Edit to add a validation function for completing this action; validation runs each time.
• Post‑completion action: click Edit to add a function that runs automatically after the action completes; it runs each time.

picture coming soon:

3.2.6 Repeating action operation example

As shown below:

picture coming soon:

4. SOP — Sign‑in / Check‑in (Process Timekeeping)

Scenario: require engineers to sign in before executing on‑site actions

Process check‑in: optional. When enabled, engineers must sign in before starting action items. Engineers must complete all process sign‑outs before completing the SOP.

• You must select a check‑in scenario. See Check‑in Scenarios for details — distance validation, micro‑adjust range, photo check‑in watermark/range, international check‑in, etc., are covered in Work Order Check‑in Management.

picture coming soon:

4.1 Process check‑in (single)

Scenario: suitable for on‑site services that finish in a single visit or day.

• Click a process to enable process check‑in.
• Select a check‑in scenario. See Check‑in Scenarios and Work Order Check‑in Management for details on distance validation, micro‑adjustment, photo check‑in, watermark, etc.
• You can choose standard check‑in or photo check‑in. After check‑in, records are stored on the Work Order Check‑in Record object. (Photo check‑in watermark settings and scope: see Photo Check‑in and Photo Watermark.)
• You can configure re‑sign (reschedule) rules: reschedule time window and reschedule content.

picture coming soon:

4.2 Process check‑in (repeating multiple times)

Scenario: process check‑in optional. When enabled, engineers must sign in before starting actions and must complete all process sign‑outs before completing the SOP.

• Allow repeat check‑ins: engineers can repeatedly check in and perform actions within the process before completing all actions. When repeat check‑in is enabled, after sign‑in the UI shows a “Sign‑out Exit” button. Clicking “Sign‑out Exit” lets the engineer later click “Sign‑in” again to reactivate the process and continue actions. Clicking “Complete and Sign‑out” marks the process as completed.
• Missing sign‑out correction: check‑in records that have sign‑in but no sign‑out will change to “missing sign‑out” at 23:59 that day; users may then complete a make‑up sign‑out.

picture coming soon:

Example:

picture coming soon:

5. Global repeating actions and repeat check‑in for SOPs

1. Enable repeating actions in the Global Settings panel

picture coming soon:

5.1 Global repeating actions

Usage scenario: for on‑site work that lasts several days but some tasks occur only when needed.

1. Click “Add Repeating Action,” then click Node Settings on the right to configure the repeating action.

• Create related record
• Add inspection group

1. Set assignee: Engineer or Related_Service_Personnel

2. Repeat frequency: Unlimited repeats (after action completes the system waits 5 minutes then creates a new pending action) or Once per day (system creates a pending action at 00:00 daily) until the entire SOP node is completed.

picture coming soon:

5.2 Global repeating check‑in

Usage scenario: suitable for on‑site work spanning multiple days where actions execute in no fixed order but daily check‑in reporting is required; also useful to record intermittent waiting time (for example, parts not yet delivered and you need to log wait time).

1. Click “Add Repeating Action,” then click Node Settings on the right.
2. Select action: Check‑in, and configure the check‑in scenario.
3. Assignee: Engineer or Related_Service_Personnel

picture coming soon:

6. Workflow Node: On‑site Standard Operating Procedure

Configure an “On‑site Standard Operating Procedure” node in your workflow so engineers perform on‑site work and execute process actions.

Note: one workflow node can only execute a single SOP template. The assignees used in this node are those defined in SOP action settings.

• SOP Template: 1) Select a specific template; or 2) Match by rule using SOP template’s applicable scope + priority. If no template matches by rule, you may choose “Auto‑complete this node” as a fallback.
• Operation button: you can customize the primary action button label and hide the “Complete” button in the to‑do list if needed.

picture coming soon:

picture coming soon: