Work Order/Equipment Service Report Generation

1. Work Order Service Report Generation

1.1 Generate Service Report in Standard Operation (SOP)

• Generate service report: In a standard operation (SOP), you can add an action to generate a service report. The engineer must complete all required actions before generating the service report. See the SOP template guide: https://help.fxiaoke.com/1a54/4107/2f99/5ee8/d486/e606
• Note: Generating a service report currently does not support “completion condition” validation or “post-completion actions”.

picture coming soon:

picture coming soon:

1.2 Quick Button to Generate Service Report

“Generate Service Report” permission: This is part of the standard Work Order feature permissions. Assign this permission to service engineers who are dispatched on Work Orders.

picture coming soon:

“Generate Service Report” visibility conditions: This is a standard business button permission. In the Business Button configuration, set the conditions that allow generating the service report.

picture coming soon:

picture coming soon:

1.3 Generate Work Order Service Report from a Workflow Node

You can configure a Service Report node in the workflow. During workflow transitions, engineers can generate the service report.

• Service report primary object: Work Order
• Service report template: 1) You can select a specific template. 2) Use rule-based matching combined with the template’s scope and priority to find a matching template. If no template matches, you can choose to “auto-complete this node” or apply a fallback rule.
• Action button: The primary action button label is customizable. You can hide the To-Do list’s “Complete” button.
• Assignee: The default assignee is the Work Order personnel field “Service Engineer”.

picture coming soon:

picture coming soon:

2. Device Service Report Generation

2.1 Generate Device Service Report from Standard Operation or Device SOP

• (Single-device Work Order) Generate service report: In a standard operation, you can add an action to generate a service report where the primary object is Work Order.Device. The engineer must complete all required actions before generating the service report. See the SOP template guide: https://help.fxiaoke.com/1a54/4107/2f99/5ee8/d486/e606
• Note: Generating a service report currently does not support “completion condition” validation or “post-completion actions”.

picture coming soon:

• (Multi-device Work Order) Generate service report: In a device standard operation, you can add an action to generate a service report where the primary object is Device. The engineer must complete all required actions before generating the service report. See the Device SOP (gray release) guide: https://help.fxiaoke.com/1a54/4107/2f99/5ee8/d486/eaac
• Note: Generating a service report currently does not support “completion condition” validation or “post-completion actions”.

picture coming soon:

2.2 Generate Device Service Report from a Workflow Node

(Single-device Work Order) You can configure a Service Report node in the workflow. During workflow transitions, engineers can generate the device service report.

• Service report primary object: Work Order.Device
• Service report template: 1) You can select a specific template. 2) Use rule-based matching combined with the template’s scope and priority to find a matching template. If no template matches, you can choose to “auto-complete this node” or apply a fallback rule.
• Action button: The primary action button label is customizable. You can hide the To-Do list’s “Complete” button.
• Assignee: The default assignee is the Work Order personnel field “Service Engineer”.

picture coming soon:

2.3 Generate Service Reports via Scheduled Task + Function

Applicable scenario: Automatically trigger scheduled tasks, e.g., on the 1st of every month send each device’s service report PDF to the device’s Account.Email.

1. Use a scheduled task to generate a service report for each device on the 1st of every month and store it in the Service Report object.

Example function:

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(“Create service report failed: “ + errMsg); return errMsg; } return “Create service report result: “ + createResult;