This commit is contained in:
2023-01-04 23:06:17 +00:00
parent d4d45e2a3c
commit 98798ab31c
2 changed files with 41 additions and 32 deletions

View File

@@ -118,6 +118,12 @@ For example if your default translation is English and you have renamed an objec
This will avoid issues with documentation and some areas of the UI being in conflict with other areas and ensure the new, clearer translations are displayed.
### Custom fields
Custom fields are migrated with a slight change: the custom field numbering in AyaNova 8 starts at "1" instead of "0" as it did in AyaNova 7.
In other words the AyaNova 7 field Custom0 will be migrated to the AyaNova 8 field Custom1, AyaNova 7's Custom1 would be AyaNova 8 Custom2 etc.
### Wiki embedded files
- In V8 Wiki embedded files are now [Attachments](ay-start-form-attachments.md) and are separate from the Wiki page.

View File

@@ -40,12 +40,12 @@ Starting with AyaNova 8 we are including previously optional add-on products at
The following add-on's from AyaNova 7 are either included or built in features of AyaNova 8 at no extra cost:
- Import / export (including updating) is now built in and expanded
- WBI web browser interface is built in
- RI responsive interface for smaller screen devices is built in
- QuickNotify direct user notification is now a built in feature
- [QBI QuickBooks desktop edition interface](integration-qbd.md) for AyaNova 8 is included at no extra cost
- More on the way
- Import / export (including updating) is now built in and expanded
- WBI web browser interface is built in
- RI responsive interface for smaller screen devices is built in
- QuickNotify direct user notification is now a built in feature
- [QBI QuickBooks desktop edition interface](integration-qbd.md) for AyaNova 8 is included at no extra cost
- More on the way
### Licensing simplified
@@ -71,11 +71,11 @@ In order to support the front end "client" devices using AyaNova, there is now a
AyaNova 8 interface features a familiar layout that has been re-designed to improve usability over AyaNova 7.
- modern, clean uncluttered interface
- simple, sharp scalable SVG icons that look sharp on any device
- now _every_ form can be easily [customized](ay-customize.md) to remove unused fields
- more working area screen space freed up
- simplified work orders, quotes and PM's with more features but only visible when you use them
- modern, clean uncluttered interface
- simple, sharp scalable SVG icons that look sharp on any device
- now _every_ form can be easily [customized](ay-customize.md) to remove unused fields
- more working area screen space freed up
- simplified work orders, quotes and PM's with more features but only visible when you use them
## Existing feature changes
@@ -198,10 +198,10 @@ For this reason the v7 templates feature is no longer required and has not been
The [work order status](svc-work-order-status.md) feature has been greatly expanded into a set of powerful features that can support process control with:
- tracking of every change of status (who and when visible right inside the work order)
- restrictions by security role of who can set or unset any status (this allows for controlling the entire service process from creation to final billing or follow up)
- locking status which when selected freezes a work order (replaces the v7 "Service completed" checkbox)
- completed type status to indicate a work order is completed which can be used with notification etc (replaces the v7 "Closed" checkbox)
- tracking of every change of status (who and when visible right inside the work order)
- restrictions by security role of who can set or unset any status (this allows for controlling the entire service process from creation to final billing or follow up)
- locking status which when selected freezes a work order (replaces the v7 "Service completed" checkbox)
- completed type status to indicate a work order is completed which can be used with notification etc (replaces the v7 "Closed" checkbox)
These new features are optional and not necessary to use if just a simple status indicator is desired and it can be used in much the same way as in v7 if there isn't a need for the extra features.
@@ -291,6 +291,10 @@ This gives a lot of flexibility in cases where a certain class or type of part f
There are now also features for maximum response time that tie into notification and close by date features of a work order automatically for contracts that include a response time commitment.
### Custom fields
In v8 all main objects support custom fields and now there are 16 of them versus 10 in AyaNova 7.
### Localized text is now Translation
Localized text has been renamed to [Translation](adm-translations.md)
@@ -343,17 +347,17 @@ In v8 we have expanded this feature into a full [Event log](adm-history.md) that
The following objects from v7 have been replaced by tags in v8:
- User certification
- User skill
- Client group
- Dispatch zone
- Part category
- Regions
- Scheduleable user group
- Unit service type
- Unit model category
- Work order category
- Work order item type
- User certification
- User skill
- Client group
- Dispatch zone
- Part category
- Regions
- Scheduleable user group
- Unit service type
- Unit model category
- Work order category
- Work order item type
[Migrating from v7](ops-import-v7.md) will automatically create tags for these objects and will then tag the corresponding objects that were set to these category items with the new tags created.
@@ -383,14 +387,13 @@ Now, a Wiki document is edited using [Markdown](https://en.wikipedia.org/wiki/Ma
Previously users were able to embed files into a Wiki document which was in turn stored directly in the AyaNova database which could cause issues and lead to longer backup and restore times.
In v8 we have expanded and improved this into it's own separate [Attachments](ay-start-form-attachments.md) feature
All v7 "Assigned docs" and wiki embedded file features have been consolidated in v8 into a new [Attachments](ay-start-form-attachments.md) feature:
- in v7 embedded wiki files were stored _inside_ the database, now Attachments are stored in a special AyaNova controlled folder in the file system to avoid bloating the database
- In v7 Documents were simply links to existing files visible to the workstations / server; file attachments are stored in a special folder managed by the AyaNova server making it easier to backup and restore and ensure all data is consolidated in one folder
- Rename - can now rename an attached file
- Notes - there is now a notes field
- in v7 embedded wiki files were stored _inside_ the database, now Attachments are stored in a special AyaNova controlled folder in the file system to avoid bloating the database
- In v7 Documents were simply links to existing files visible to the workstations / server; file attachments are stored in a special folder managed by the AyaNova server making it easier to backup and restore and ensure all data is consolidated in one folder
- Rename - can now rename an attached file
- Notes - there is now a notes field
- All business objects in v8 support attachments
### Display formats