Editing Work Order State History Records |
This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.4.
For the latest version of this help file can be found here.
< Previous section | Table of Contents | Index | Next section >
Various actions change the state of a work order. For example, Void changes a work order from the Draft state to the Void state. When you change the state of a work order, MainBoss may open a window where you can record comments about what you're doing. This window also lets you specify the effective date of the change; for example, if you close a work order the day after the job actually finishes, you may want to backdate the state change record to indicate when the job was actually finished.
The editor window normally contains the following:
Number: A read-only field identifying the work order whose state is changing.
Current State History State: A read-only field giving the current state of the work order (the state before the intended change).
Current State History Status: A read-only field giving the current status of the work order. For more on work order statuses, see Work Order Status Codes.
Effective Date: The date that you want to associate with the change.
User Contact: A read-only field identifying the person who created this record.
State: A read-only field giving the state that the work order will enter once you Save & Close this record.
Status: A new status code that you want to assign to this work order. Typically, a status code should only be assigned to a work order when the work order needs attention from someone; otherwise, the status should be blank.
Comments: Any comments you want to record.
Save & Close: Saves the current record and closes the editor window. This changes the state of the work order.
Close: Closes the window without changing the state of the work order.
For more on work orders, see Work Orders. For more on viewing work orders, see Viewing Work Orders. For more on editors in general, see Using Editors.
< Previous section | Table of Contents | Index | Next section >