Work Orders Created from Tasks

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.2.
For the latest version of this help file can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

Tasks provide a description of work to be done in planned maintenance. However, you may also want to perform the work as an unscheduled job. For example, you may want to perform an oil change on a car even though the car isn't due for an oil change yet.

In this case, you can create a one-off work order based on the information in a task record. This lets you create a work order very quickly—all you have to do is fill in the name of the unit, and a few other fields.

To create a work order from a task, select the task in the Tasks viewer, then click New Work Order From Task. This opens a window that contains the following:

Task: Specifies the task record to use as the basis for the new work order.

For Access Code options: Let you specify what to do when the access code for a task is different from the access code for the unit:

Prefer value from Task: If both the task and the unit record specify an access code, MainBoss uses the access code from the task. However, if the task record doesn't have an access code, MainBoss uses the code from the unit.

Prefer value from Unit: If both the task record and the unit record specify an access code, MainBoss uses the access code from the unit. However, if the unit record doesn't have an access code, MainBoss uses the code from the task.

Only use value from Task: MainBoss always uses the access code from the task record. (If the task record doesn't have an access code, the generated work order won't have an access code either.)

Only use value from Unit: MainBoss always uses the access code from the unit record. (If the unit record doesn't have an access code, the generated work order won't have an access code either.)

For Expense Model options: Let you specify what to do when the expense model for a task is different from the one for the unit. The options work the same way as the options in For Access Code.

Purchase Order initial State override: Lets you specify an initial state for any purchase orders generated in connection with this task.

Purchase orders will be generated from any purchase order templates associated with the task. Each template may have a default initial state associated with it: Closed, Issued, Open, or Voided. By default, generated purchase orders are put into the specified state; however, you can override the default by specifying a different state in this field.

Work Order initial State override: Similar to "Purchase Order initial State override". By default, each generated work order is created in the draft state. However, you may wish to put generated work orders into some other state instead—most likely the open state, indicating that the work order is ready to be printed. (Remember though that if a work order is open, some of its information is locked down and can't be changed unless you first Suspend the work order.)

Number: Identifies the new work order. MainBoss automatically generates a new work order number.

Unit: The unit on which you want the work to be done.

Work Start Date: The date you want the work to begin.

Subject: A read-only field giving the subject line to be used for the work order.

Access Code: A read-only field giving the access code to be used for the work order (determined by the "For Access Code" options).

Expense Model: A read-only field giving the expense model to be used for the work order (determined by the "For Expense Model" options).

Save & Close: Creates the desired work order and closes the window.

Cancel: Discards any changes that you've made. The button then changes to Close, which will close the window without creating a work order.

Close: Closes the window without creating a work order.

For more on tasks, see Tasks. For more on work orders, see Work Orders.

< Previous section  |  Table of Contents  |  Index  |  Next section >