This commit is contained in:
BIN
docs/8.0/ayanova/docs/img/svc-wo-labor-context-menu.png
Normal file
BIN
docs/8.0/ayanova/docs/img/svc-wo-labor-context-menu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
BIN
docs/8.0/ayanova/docs/img/svc-wo-labor-context.png
Normal file
BIN
docs/8.0/ayanova/docs/img/svc-wo-labor-context.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
@@ -107,7 +107,6 @@ Limited access roles are restricted in what they can see and do on the work orde
|
||||
3. View only the header Customer name and Contact fields
|
||||
4. Convert to Labor menu item available
|
||||
|
||||
|
||||
## How to access Work orders
|
||||
|
||||
Work orders are accessed in the following ways:
|
||||
@@ -115,8 +114,7 @@ Work orders are accessed in the following ways:
|
||||
- From the [Personal schedule](home-schedule.md) form when scheduled on a work order
|
||||
- From the [Service schedule](svc-schedule.md) form for any User scheduled on a work order
|
||||
- From the `Service` navigation pane `Work orders` item to open the Work orders [data table](ay-start-form-data-tables.md)
|
||||
- From any [data table](ay-start-form-data-tables.md) column showing Work orders such as the [Customers](customers.md) *Last work order* column
|
||||
|
||||
- From any [data table](ay-start-form-data-tables.md) column showing Work orders such as the [Customers](customers.md) _Last work order_ column
|
||||
|
||||
## Work orders data table
|
||||
|
||||
@@ -126,12 +124,11 @@ The Work orders [data table](ay-start-form-data-tables.md) lists all the Work or
|
||||
|
||||
The work order edit form provides all the [standard edit form](ay-start-edit-forms.md) functionality and additional fiels and features outlined below:
|
||||
|
||||
This form is designed to display as simply as possible and will not display a section unless it's been *added* to the work order. For example if no Travel records are entered the Travel section is not displayed at all.
|
||||
This form is designed to display as simply as possible and will not display a section unless it's been _added_ to the work order. For example if no Travel records are entered the Travel section is not displayed at all.
|
||||
|
||||
This means you can use any features you need and unused features will not take up space.
|
||||
|
||||
If you know you will *never* require a feature or some fields within a section you can remove then from the Work order form using the [form customization](ay-customize.md) feature of AyaNova.
|
||||
|
||||
If you know you will _never_ require a feature or some fields within a section you can remove then from the Work order form using the [form customization](ay-customize.md) feature of AyaNova.
|
||||
|
||||
### User interface work order structure
|
||||
|
||||
@@ -139,20 +136,50 @@ The user interface mirrors the logical structure of a work order with a single h
|
||||
|
||||
Clicking on a row in a table on the work order form opens that record for editing below the table.
|
||||
|
||||
### How to use the table collections
|
||||
#### Tables on narrow screen devices
|
||||
|
||||
When AyaNova doesn't have enough width to display a full table it switches to a vertical display instead to avoid the need to scroll sideways. See the [data table](ay-start-form-data-tables.md) help page for more information. For the purposes of this help page we'll show full width tables but the functionality is the same.
|
||||
|
||||
### How to use the work order item grand child collections
|
||||
|
||||
All items below the Work order Item level are collections that display as a single edit form when there is only one in the collection or as a table when there are multiple items in that collection.
|
||||
|
||||
For example, if there is a single Unit there is no need to take up space showing a table of one Unit so it displays as a single edit form area showing the fields of the work order item Unit record. However, if there are two or more Units then a table displays showing each Work order Item Unit record in a row and clicking on a row opens the edit form area below the table so _that_ particular row can be edited.
|
||||
For example, if there is a single Unit there is no need to take up space showing a table of one Unit so it displays as a single edit form area showing the fields of the work order item Unit record. However, if there are two or more Units then a table appears with rows representing each Work order Item Unit record in a row.
|
||||
|
||||
This pattern is used for all the collections below the header so that the simplest possible interface is shown at all times.
|
||||
|
||||
#### Selecting records for editing
|
||||
|
||||
When there are multiple grand child records such as work order item labor records, clicking on a row in the collections table will select that record and the edit form below the collections table will switch the record selected for editing.
|
||||
|
||||
The context menu for each collection will often have options that act on a selected record so you won't actually see the option in the menu *until* a record is selected. When there is only one record it is by default the selected record.
|
||||
|
||||
#### Adding and deleting collection items
|
||||
|
||||
Each collection has a context menu button to the right of it's title:
|
||||
|
||||

|
||||
|
||||
Clicking on this button will open the context menu with options for _that_ particular type of item.
|
||||
|
||||

|
||||
|
||||
Here we see the Labor items context menu. There are three options common to all collections:
|
||||
|
||||
- _New_ `+` option is used to add a new record. The record is added here locally to be filled out in the form below the collection table and later saved to the server.
|
||||
- _Mark for deletion_ is available because we have a record selected in the collection table by previously clicking on a row. The record will not be deleted until the entire work order is saved.
|
||||
- _Mark all for deletion_ is used to delete **all** records represented by their rows in the collection table. The records will not be deleted until the entire work order is saved.
|
||||
|
||||
Each type of collection has it's own particular set of context menu options documented in their sections below.
|
||||
|
||||
### Header
|
||||
|
||||

|
||||
|
||||
A work order has a single Header section which contains information and fields related to the entire work order.
|
||||
|
||||
|
||||
|
||||
### Work Order Items
|
||||
|
||||

|
||||
|
||||
Reference in New Issue
Block a user