Enabling tasks as work orders

For scheduling and tracking purposes, some businesses want to process work tasks as work orders. To view tasks as work orders in Work Supervision and Work Execution Work Centers, administrators must configure the object structure for work orders.

About this task

Businesses can choose to process work order tasks as separate work orders. For example, when a work order for an office renovation includes electrical work and painting, you might want to display the electrical task as a work order for the electrician and the painting task as a work order for the painter.

By default, tasks are not processed as work orders. The following procedures explain how to enable tasks as work orders for your Work Supervision and Work Execution Work Centers.

Enabling tasks as work orders for technicians

To enable tasks as work orders for technicians, an administrator must configure the query clause for technicians.

About this task

To configure tasks as work orders for technicians, an administrator must edit the uxtechnicianownerfilter query clause in the MXAPIWODETAIL object structure.

Procedure

  1. In the Object Structures application, filter to locate the MXAPIWODETAIL object structure and select that object.
  2. From the More Actions menu, select Query Definition.
  3. In the Query Definition window, filter for the uxtechnicianownerfilter query clause.
  4. Expand the row for the query clause.
  5. In the Query Clause field, specify the appropriate clause for your needs, as shown in the following table.
    To enable tasks as work orders, the istask parameter must be set to istask=1.
    Table 1. Sample code for technician query clauses
    To display the following information... Specify this query
    Technician sees only regular work orders.

    This option is the default. To keep this option, no action is needed.

    owner = :&personid& or ownergroup 
    in (select persongroup from persongroupteam 
    where respparty=:&personid&) and istask=0
    Technician sees only task work orders.
    owner = :&personid& or ownergroup in 
    (select persongroup from persongroupteam 
    where respparty=:&personid&) and istask=1
    
    Technician sees both task and regular work orders.
    owner = :&personid& or ownergroup in 
    (select persongroup from persongroupteam 
    where respparty=:&personid&) 
  6. Click OK.

Results

After you complete the configuration, if you specify the value 1 for the istask parameter in the query, tasks are displayed as work orders.

Enabling tasks as work orders for supervisors

To enable tasks as work orders for supervisors, an administrator must configure the query clauses for supervisors.

About this task

To configure tasks as work orders for supervisors, an administrator must edit the following query clauses in the MXAPIWODETAIL object structure: APPROVEWORK, CLOSEWORK, MONITORWORK, FINDOWNERWORK, and CLOSEDWORK.

Procedure

  1. In the Object Structures application, filter to locate the MXAPIWODETAIL object structure and select that object.
  2. From the More Actions menu, select Query Definition.
  3. In the Query Definition window, filter for the query clause that you want to update.
  4. Expand the row for the query clause.
  5. In the Query Clause field, specify the appropriate clause for your needs, as shown in the following table:
    Table 2. Sample code for supervisor query clauses
    To display the following information... Specify this query
    Supervisor sees only regular work orders.

    This option is the default. To keep this option, no action is needed.

    (woclass =(select value from 
    synonymdomain where domainid ='WOCLASS' and 
    maxvalue = 'WORKORDER') and historyflag=0 and 
    istask=0 and supervisor=:&personid&)
    Supervisor sees only task work orders.
    (woclass =(select value from 
    synonymdomain where domainid ='WOCLASS' and 
    maxvalue = 'ACTIVITY') and historyflag=0 and 
    istask=1 and supervisor=:&personid&)
    Supervisor sees both task and regular work orders.
    (woclass IN (select value from 
    synonymdomain where domainid ='WOCLASS' and 
    maxvalue IN ('ACTIVITY','WORKORDER')) and 
    historyflag=0 and supervisor=:&personid&)
  6. Click OK.