This commit is contained in:
2022-02-03 22:25:54 +00:00
parent 5d5bb6e20b
commit a572b30407
5 changed files with 32 additions and 3 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

View File

@@ -149,9 +149,9 @@ Clicking on it again reveals a much larger set of items:
![Work order walkthrough 17](img/svc-work-order-walk17.png)
All of these items are optional and none of them will appear on the work order form unless that type of object is added.
All of these items are optional and none of them will appear on the work order form unless that type of object is added.
Because we are intended to service a specific piece of equipment owned by the Customer and we want to keep track of it in AyaNova we will add this Unit to be serviced to the work order so we'll click on the _Work order item unit_ option in _Add_ section of the menu.
Because we are intended to service a specific piece of equipment owned by the Customer and we want to keep track of it in AyaNova we will add this Unit to be serviced to the work order so we'll click on the _Work order item unit_ option in _Add_ section of the menu.
![Work order walkthrough 18](img/svc-work-order-walk18.png)
@@ -161,7 +161,7 @@ We'll go ahead and select a Unit and also save the Work order again since we've
![Work order walkthrough 19](img/svc-work-order-walk19.png)
The Unit has been added and some desriptive information about it is displayed in the work order item Units table. The other fields here in the work order item Unit record are optional, (we could even [hide them](ay-customize.md) if we don't need them). Nothing more needs to be done here so we'll now schedule a service technician to do the work.
The Unit has been added and some desriptive information about it is displayed in the work order item Units table. The other fields here in the work order item Unit record are optional, (we could even [hide them](ay-customize.md) if we don't need them). Nothing more needs to be done here so we'll now schedule a service technician to do the work.
#### Schedule a service technician
@@ -169,6 +169,35 @@ A service technician is scheduled on a work order by adding a work order item sc
![Work order walkthrough 20](img/svc-work-order-walk20.png)
A new, empty Work order item Scheduled User record is now added to the work order.
![Work order walkthrough 21](img/svc-work-order-walk21.png)
We'll go ahead and select the service technician we want to assign this work to, set a date and time for service and pick a suggested service rate.
![Work order walkthrough 22](img/svc-work-order-walk22.png)
Once we save this work order, Lamar the technician selected will see this item appear in their personal [schedule form](home-schedule.md) and it will also appear on the [Service schedule form](svc-schedule.md) that shows all scheduled technicians for overall service management.
At this point the work order is completed for scheduling purposes.
Once the Unit is serviced by Lamar, he will fill out the billable details in the work order by creating a Work order item Labor record. AyaNova has a shortcut to save time - the Scheduled user record can be turned into a Labor record with a click from the Scheduled Users area context menu:
![Work order walkthrough 23](img/svc-work-order-walk23.png)
The *Convert to labor* menu item creates a new work order item Labor record, adds it to the current work order item and copies the details from the Scheduled user record:
![Work order walkthrough 24](img/svc-work-order-walk24.png)
All that remains to be done here is for Lamar to optionally enter the details of the work he has done in the *Service details* field which will display on the various reports and be recorded for future reference.
At this point this work order is completed and ready for invoicing.
00000000000000000000000000000000000000
## How to use collections