This commit is contained in:
@@ -8,11 +8,11 @@ The top portion of an edit form ("App bar") is the primary source for navigation
|
||||
|
||||

|
||||
|
||||
This app bar is green indicating the User has the ability to edit the current record.
|
||||
The app bar in the image above is green indicating the User has the ability to edit the current record.
|
||||
|
||||

|
||||
|
||||
This app bar is grey indicating the User is not permitted to to edit the current record. Grey app bars can indicate an object is also in a read-only state rather than the User not having sufficient privileges. For example when a service work order is temporarily set to a read only status.
|
||||
The app bar in the image above is grey indicating the User is not permitted to to edit the current record. Grey app bars can indicate an object is also in a read-only state rather than the User not having sufficient privileges. For example when a service work order is temporarily set to a read only status.
|
||||
|
||||
#### App bar controls
|
||||
|
||||
@@ -38,7 +38,7 @@ The notification bell icon is always visible in AyaNova and indicates when there
|
||||
|
||||
When there is enough width to fit, AyaNova will "surface" commonly used menu icons to save a click. Generally this is the "Save" button on most forms.
|
||||
|
||||
#### Menu icon
|
||||
##### Menu icon
|
||||
|
||||
Menu's that can be opened are always represented in AyaNova by the three vertical dots icon. Menus at the top of edit forms contain controls related to the overall object. Menus inside the edit form contain controls related to a specific sub-section of the edit form. Look for menu controls to see further actions that can be taken in forms.
|
||||
|
||||
@@ -84,7 +84,7 @@ When the save button is disabled it means that there were no changes detected th
|
||||
|
||||
The delete button permanently removes the record from the server. If the button is not present or grayed out it means there is insufficient rights to delete the object or it is not deleteable for other reasons indicated.
|
||||
|
||||
If a record is deleted but is found to be linked to other objects at the server an error message will be returned indicating it is not deleteable due to this condition and which types of other objects this object is linked to in case the User wants to track down and remove all connections so they can delete this object.
|
||||
If an object that is being deleted is found to be linked to other objects at the server, an error message will be returned indicating it is not deleteable due to this condition and which types of other objects this object is linked to in case the User wants to track down and remove all connections so they can delete this object. For example attempting to delete a Customer that is selected on work orders.
|
||||
|
||||
#### Report
|
||||
|
||||
@@ -106,7 +106,9 @@ Duplicate is particularly useful when creating a new object that shares many sim
|
||||
|
||||
#### View on map
|
||||
|
||||
Edit forms for objects with [address controls](ay-start-common-controls.md#address) will have a "View on map" menu item which when clicked will attempt to display the current objects location on a map provided there is enough information to determine the location. The most accurate location is had by entering the latitude and longitude into the fields provided in the "Street" address section however most map providers can match to a postal code or street address when required.
|
||||
Edit forms for objects with [address controls](ay-start-common-controls.md#address) will have a "View on map" menu item which when clicked will attempt to display the current objects location on a map provided there is enough information to determine the location. The most accurate location is had by entering the latitude and longitude into the fields provided in the "Street" address section however most map providers can match to a postal code or street address when required.
|
||||
|
||||
AyaNova can automatically fill in the latitude and longitude when using a supported device see the [address controls](ay-start-common-controls.md#address) documentation for details.
|
||||
|
||||
For items that are mobile or may not have a street address such as a Customer unit in remote locations the latitude and longitude are provided for mapping and location purposes.
|
||||
|
||||
@@ -120,13 +122,13 @@ All main business objects in AyaNova are reviewable.
|
||||
|
||||
#### History
|
||||
|
||||
History menu option options the [History form](home-history.md) to display a log of events related to that object such as when it was created and each edit made to it.
|
||||
History menu option opens the [History form](ay-history.md) to display a log of events related for this object being edited such as when it was created and each edit made to it etc.
|
||||
|
||||
All main business objects in AyaNova have their own history event log.
|
||||
All main business objects in AyaNova are tracked in the history event log.
|
||||
|
||||
#### Customize
|
||||
|
||||
If the logged in User has sufficient rights they will see a Customize menu option allowing for form customization which is documented fully in [customize form](ay-customize.md) documentation page.
|
||||
If the logged in User has sufficient rights they will see a Customize menu option allowing for form customization which is documented fully in the [customize form](ay-customize.md) documentation page.
|
||||
|
||||
#### Search
|
||||
|
||||
@@ -138,4 +140,4 @@ Help menu option opens the specific help documentation for that form.
|
||||
|
||||
### Common edit form controls
|
||||
|
||||
Controls used in AyaNova are documented on the [Common controls](ay-start-common-controls.md) documentation page.
|
||||
Controls used in AyaNova are documented on the [Common form controls](ay-start-common-controls.md) documentation page.
|
||||
|
||||
Reference in New Issue
Block a user