Work Order/Equipment Service Report Generation

I. Work Order Service Report Generation

1.1 Generating Work Order Service Reports in Standard Operations

• Generating Service Reports: In standard operations, you can add a “Generate Service Report” action that requires engineers to complete all mandatory steps before generating the report. Refer to the Field Standard Operating Procedure (SOP) Template for detailed instructions.
• Note: The “Generate Service Report” feature currently does not support “Completion Condition” validation or “Post-Completion Actions”.

picture coming soon:

picture coming soon:

1.2 Generating Service Reports via Quick Action Button

• “Generate Service Report” Permission: A standard Work Order permission assigned to service engineers.
• Visibility Conditions: Configured in the business button settings to define when the “Generate Service Report” button appears.

picture coming soon:

picture coming soon:

picture coming soon:

1.3 Generating Work Order Service Reports via Service Process Nodes

Configure a service report node in the workflow to allow engineers to generate reports during process execution.

• Primary Object: Work Order
• Report Template:
  1) Select a specific template, or
  2) Use rule-based matching (template applicability + priority). If no template matches, choose “Auto-Complete Node” or a fallback rule.
• Action Button: Customize the main button label and hide the “Complete” button in the task list if needed.
• Assignee: Default assignee is the “Service Engineer” field in the Work Order.

picture coming soon:

picture coming soon:

II. Equipment Service Report Generation

2.1 Generating Equipment Service Reports in Standard Operations

• (Single-Equipment Work Order): Add a “Generate Service Report” action in standard operations with the primary object set to “Work Order.Equipment”. Engineers must complete all mandatory steps. Refer to the Field SOP Template.
• (Multi-Equipment Work Order): Add the action in equipment standard operations with the primary object set to “Equipment”. Refer to the Equipment Field SOP (Beta).
• Note: The feature does not support “Completion Condition” validation or “Post-Completion Actions”.

picture coming soon:

picture coming soon:

2.2 Generating Equipment Service Reports via Service Process Nodes

• Primary Object: Work Order.Equipment
• Template Rules: Same as Section 1.3.
• Assignee: Default is the “Service Engineer” field in the Work Order.

picture coming soon:

2.3 Generating Service Reports via Scheduled Tasks + Functions

Use Case: Automatically trigger tasks (e.g., email equipment service reports in PDF format to the “Account.Email” field on the 1st of each month).

1. Use scheduled tasks to generate reports for each equipment on the 1st of the month and store them in the Service Report object.

Example Function:

```groovy Map header = [ “Content-Type”: “application/json;charset=UTF-8”, “x-fs-methodname”: “createServiceReportDirect” ]; Map args = [ “casesId” : context.data._id, // Work Order ID “serviceReportTemplateId” : 92, // Service Report Template ID ]

Map requestParam = [“args”: args]; def ret = Fx.proxy.callAPI(“eservice.proxy”, header, requestParam); HttpResult result = ret.data as HttpResult; log.info(result); Map content = result.content as Map; String errCode = content[“errCode”]; String errMsg = content[“errMsg”]; Boolean createResult = content[“data”]; if (errCode != ‘C120040000’) { log.info(“Failed to generate service report: “ + errMsg); return errMsg; } return “Service report generation result: “ + createResult; ```