Service Management Manuals

Appearance

Verify dispatch fields and results ​

Overview ​

Dispatch, intra-group dispatch, transfer, and reassignment will backfill the work order fields. Before going online, you should check the field values and the current process task handler at the same time to avoid only seeing the work order field updates but missing that the to-do still belongs to the old person.

Before you begin ​

  • Prepare direct engineers, internal service groups, service providers and external service groups for testing process.
  • Administrators can view work order fields and process task handlers.
  • Manual dispatch and automatic dispatch of test work orders have been distinguished.

Procedure ​

1. Verify enterprise-level dispatch ​

  1. Manually and automatically assign engineers once each to check assign_user, assign_way__c, assign_time__c, field_xcfwry__c and related_service_personnel__c.
  2. Complete the assignment of service groups manually and automatically once each, and check the service group field_serviceGroupName__c or the service provider service group out_service_group_id.
  3. When confirming automatic dispatch, the dispatcher field is empty.

2. Dispatch within the verification team ​

  1. Complete one manual dispatch and one automatic assignment within the service group.
  2. Check the dispatch time service_group_assign_time__c, method service_group_assign_way__c and engineer fields in the group.
  3. Check the Service Group Dispatcher field. The sources are recorded as service_group_assign_user and out_service_group_assign_user respectively and cannot be directly combined into the same meaning.
  4. Confirm the actual API Name in the current tenant field, and record whether it applies to the internal service group or the external service provider service group.

3. Verify orders dispatched by service provider ​

  1. After the enterprise selects a service provider, it checks the service implementation partner field_partner__c.
  2. For existing enterprises opened before version 880, check whether the downstream service provider field_fwssf__c is used.
  3. Check the service provider’s dispatcher out_assign_user, dispatch time out_assign_time__c, dispatch method out_assign_way__c and service provider’s engineer field_outDealUser__c.
  4. Check the docking company name and ID fields as needed.

4. Verification of transfer and reassignment ​

  1. Check the engineer and collaborative engineer fields after assigning or reassigning engineers.
  2. Check the service group field after reassigning the service group.
  3. Open the current process task and confirm that the handler is synchronized to the new engineer or dispatcher of the new service group.
  4. For nodes whose handler is derived from Owner or another custom expression, verify the result after using Change Handler or a synchronization function.

Verify the result ​

  1. Manual dispatch records the operator, and the dispatcher field for automatic dispatch is empty.
  2. Enterprise-level and intra-group dispatches record their respective time, method and recipient.
  3. The service provider link records the service provider selected by the enterprise and the internal dispatch results of the service provider.
  4. After reassignment, the work order fields and process task handlers remain consistent.
  5. The conflicting field API Name has been registered according to the actual results of the tenant, rather than inferred from the source.

Notes ​

  • There are source differences between service_group_assign_user and out_service_group_assign_user, which may reflect differences in internal/external service groups or tenant versions.
  • Collaborative engineers may be saved as service personnel child objects in some existing companies.
  • Work order field updates do not guarantee automatic synchronization of all customization process tasks.