admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-02-09 18:00:27 +00:00
parent 179a401d0b
commit 8809a0a458
1 changed files with 32 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

61
docs/8.0/ayanova/docs/ay-start-changes-from-v7.md
View File

@@ -163,7 +163,7 @@ The work order items now have a "Sequence" field and can be re-ordered as desire
#### Work order item Units
Units are now a _collection_ under work order item rather than a single item. This facilitates scenarios where a large number of units need to be serviced identically at the same time (inspection, maintenance etc). Users can choose to select multiple units or a single unit as appropriate.
Units are now a _collection_ under work order item rather than a single item. This facilitates scenarios where a large number of units need to be serviced identically at the same time (inspection, maintenance etc). Users can choose to select multiple units or a single unit as appropriate.
We have also included the ability to bulk select Units from any customer, not just the one selected on the work order to support scenarios where the equipment being service may rotate between customers.
@@ -173,21 +173,21 @@ Outside service is now a _collection_ under work order item rather than a single
#### Work order item Tasks
Tasks have been changed to a collection stored _with_ the work order rather than linked to a separate collection of tasks in a [task group](svc-task-groups.md). Now, a user can simply type in a list of tasks or still select from a task group which will be used to fill in the work order rather than link to it so it can be edited as needed. In addition tasks are now re-orderable by setting a Sequence field.
Tasks have been changed to a collection stored _with_ the work order rather than linked to a separate collection of tasks in a [task group](svc-task-groups.md). Now, a user can simply type in a list of tasks or still select from a task group which will be used to fill in the work order rather than link to it so it can be edited as needed. In addition tasks are now re-orderable by setting a Sequence field.
With tasks being stored with the work order it means that Task groups and their tasks can be changed at any time without affecting existing work orders with tasks.
#### Pricing
Pricing and costs are now clearly displayed on the work order in a consistent manner between all billable items that have prices.
Pricing and costs are now clearly displayed on the work order in a consistent manner between all billable items that have prices.
List price and final price are both shown so that it's clear when a contract or manual override affects the final price.
List price and final price are both shown so that it's clear when a contract or manual override affects the final price.
Most non management roles will not see costs or in some cases prices [by default](svc-workorders.md#cost-restrictions).
Most non management roles will not see costs or in some cases prices [by default](svc-workorders.md#cost-restrictions).
Most prices (except for Parts which tend to have volatile pricing) are not stored with the work order but instead calculated on the fly when a work order is opened / printed.
Most prices (except for Parts which tend to have volatile pricing) are not stored with the work order but instead calculated on the fly when a work order is opened / printed.
This is part of the decoupling process that allows for easily changing the Contract or Customer on an existing Work order.
This is part of the decoupling process that allows for easily changing the Contract or Customer on an existing Work order.
This means that similar to v7 some items like taxes and rates cannot be changed once they have been used on a work order however Parts are an exception as the pricing is considered more volatile so part prices are "snapshotted" on being added to a work order and stored with the work order itself.
@@ -207,19 +207,19 @@ In v8 [Unit Models](svc-unit-models.md) no longer have the "Model Number" field.
### Preventive Maintenance ("PM")
[PMs](svc-pms.md) now provide all the same sections as a service Work order with the sole exception of Part Requests which are not applicable to PMs. Menu options are available to directly duplicate a PM to a Quote or Work order (and optionally WIKI and File Attachments as well). PMs can also be duplicated to a new PM.
[PMs](svc-pms.md) now provide all the same sections as a service Work order with the sole exception of Part Requests which are not applicable to PMs. Menu options are available to directly duplicate a PM to a Quote or Work order (and optionally WIKI and File Attachments as well). PMs can also be duplicated to a new PM.
The "Desired day of week" to generate the Service Work Order on has been replaced by an "Exclude days of the week" control so instead of choosing a particular day to generate to now you would choose days _not_ to generate on and the system will find the closest available day that matches that choice.
### Contracts
[Service contracts](svc-contracts.md) have been expanded with new features and more flexibility when applying them to work orders.
[Service contracts](svc-contracts.md) have been expanded with new features and more flexibility when applying them to work orders.
You can now select a discount off list price or a markup on cost for special contract pricing.
You can now select a discount off list price or a markup on cost for special contract pricing.
In addition to the v7 general discount in a contract you can now target specific parts or rates by selecting specific tags they must have for the contract to apply.
This gives a lot of flexibility in cases where a certain class or type of part for example should be included in discounts but not others.
This gives a lot of flexibility in cases where a certain class or type of part for example should be included in discounts but not others.
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.
@@ -229,33 +229,37 @@ Localized text has been renamed to [Translation](adm-translations.md)
### Security groups -> Authorization Roles
Security groups have been replaced by a **role** based authorization system.
In v7 you would select a security group for a user to restrict their access to objects in AyaNova.
In v8 a user is now assigned one or more Authorization Roles which controls their access. Roles are pre-defined and pertain to the type of user for example there are roles for Inventory, Accounting, Business administration, Technician, Subcontractor etc. Whichever roles you assign to a user give them access to those areas of AyaNova.
Security groups have been replaced by a [Roles](ay-biz-admin-roles.md) based authorization system.
Migrating Users from AyaNova 7 will automatically set migrated Users to have no role in order to protect information security; the business administrator will need to set each user to the most appropriate new roles after migration is completed. For more about migrating from a business administration standpoint see the [business administration migration guide](ay-biz-admin-migrate-v7.md) and for more about the techncial aspects of the migration process see the [Migration technical guide](ops-import-v7.md).
In v7 you would select a security group for a user to restrict their access to objects in AyaNova.
In v8 a [User](adm-users.md) is now assigned one or more [Authorization Roles](ay-biz-admin-roles.md) which control their access. Roles are pre-defined and pertain to the department or job requirements of the User for example there are roles for Inventory, Accounting, Business administration, Technician, Subcontractor etc. Whichever roles you assign to a user give them access to those areas of AyaNova.
Migrating Users from AyaNova 7 will automatically set migrated Users to have no role for security; the business administrator will need to [set each User](adm-users.md) to the most appropriate new roles after migration is completed.
For more about migrating from a business administration standpoint see the [business administration migration guide](ay-biz-admin-migrate-v7.md) and for more about the techncial aspects of the migration process see the [Migration technical guide](ops-import-v7.md).
For details see the [Authorization roles](ay-biz-admin-roles.md) guide for more information.
### Schedule markers
In AyaNova 7 there were two types of schedule markers: a regular one and a follow up type. The follow up type was tied to a particular object and provided a button to open that object. The regular type did not have a link to an object. Both had a "Completed" check box.
In AyaNova 7 there were two types of schedule markers: regular and "follow up". The follow up type was tied to a particular object and provided a button to open that object. The regular type did not have a link to an object. Both had a "Completed" check box.
In AyaNova 8 the Schedule marker has been replaced by two separate objects the "Reminder" and the "Review".
In AyaNova 8 the Schedule marker has been replaced by two separate objects the [Reminder](home-reminders.md) which is the replacement for a regular schedule marker and the [Review](home-reviews.md) object which replaces the follow up type.
#### Reminder
A Reminder is similar to a regular v7 Schedule marker and can not be tied to a particular object. It's purpose is to provide a place where a Note can be tied to a date and display in the Schedule form. Basically the original core purpose of a Schedule marker.
A [Reminder](home-reminders.md) is similar to a regular v7 Schedule marker and can not be tied to a particular object. It's purpose is to provide a place where a Note can be tied to a date and display in the Schedule form. Basically the original core purpose of a Schedule marker.
#### Review
A Review is tied to a particular object and has a Review Date and a Completed date and also displays in the graphical Schedule. It's purpose is to replace the v7 Follow Up feature and is intended for exactly that purpose: to follow up or review the status of a particular object in AyaNova be it a Customer or Unit or some other main object type.
A [Review](home-reviews.md) is tied to a particular object and has a Review Date and a Completed date and also displays in the graphical Schedule. It's purpose is to replace the v7 Follow Up feature and is intended for exactly that purpose: to follow up or review the status of a particular object in AyaNova be it a Customer or Unit or some other main object type.
### Record history
In AyaNova 7 there was a Record history feature which would show who created an object and when it was created and who last edited an object and when. No intermediate changes were tracked, in other words you couldn't see any history of changes, only the most recent.
In v8 we have expanded this feature into a full [Event log](adm-history.md) that not only trackes all changes to business objects over time, but also many other important User actions in AyaNova.
In v8 we have expanded this feature into a full [Event log](adm-history.md) that not only trackes all changes to business objects over time, but also many other important User actions in AyaNova and ties into the expanded [Notification system](home-notify-subscriptions.md).
### Tags
@@ -277,11 +281,11 @@ The following objects from v7 have been replaced by tags in v8:
[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.
In addition, all objects migrated from v7 will be tagged with "v8-migrate".
### Reports
AyaNova 8 has a built in report template editor to create and customize existing reports, however, the reporting system is completely new and not compatible with v7 style report templates which relied on a 3rd party commercial reporting component. Reporting is now HTML based and uses Javascript as the report language and HTML / Mustache template system as the report design template.
AyaNova 8 has a built in [report template editor](ay-report-edit.md) to create and customize existing reports, however, the reporting system is completely new and not compatible with v7 style report templates which relied on a proprietary 3rd party commercial reporting component and system.
All reporting in AyaNova is now open standards HTML based and uses Javascript as the report language and HTML / Mustache template system.
Reports that were customized in v7 and do not have a replacement provided with the stock v8 report templates will need to be re-created in v8.
@@ -291,18 +295,17 @@ The [Wiki](ay-start-form-wiki.md) feature has been changed substantially based o
##### Editor
Previously there was a hybrid Wiki system, remote users (WBI) would interact with an HTML editor and HTML representation of the wiki document and windows AyaNova users would interact with a "rich text" editor similar to Wordpad. This required behind the scenes translations between Rich text format and HTML format and the results were not always compatible. In addition, it would have been very difficult to edit Wiki pages on small screen devices.
Previously there was a hybrid Wiki system, remote users (WBI) would interact with an HTML editor and HTML representation of the wiki document and windows AyaNova users would interact with a "rich text" editor similar to Windows Wordpad. This required behind the scenes translations between Rich text format and HTML format and the results were not always compatible. In addition, it would have been very difficult to edit Wiki pages on small screen devices.
Now, a Wiki document is edited using [Markdown](https://en.wikipedia.org/wiki/Markdown) a simple plain text formatting language. This allows us to provide an efficient and easy to use editor for Wiki pages that will work on any AyaNova supported device.
##### Embedded files
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.
Now, we have expanded this feature into it's own separate [Attachments](ay-start-form-attachments.md) feature
### Documents / Wiki Embedded files -> Attachments
In v8 we have expanded and improved this into it's own separate [Attachments](ay-start-form-attachments.md) feature
All attached and embedded file features have been consolidated in v8 into a new [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.
- Attachment storage
- in v7 embedded wiki files were stored _inside_ the database, now Attachments are stored in a special folder in the file system to avoid bloating the database.
@@ -312,10 +315,10 @@ All attached and embedded file features have been consolidated in v8 into a new
### Display formats
In v7 there were Global settings for Part display format, Unit display format etc. In v8 this feature has been replaced by [autocomplete list control](ay-start-form-autocomplete.md) templates which allow customizing _all_ autocomplete lists to choose which fields are used for display and searching in v8.
In v7 there were Global settings for Part display format, Unit display format etc. In v8 this feature has been replaced by [autocomplete list control](ay-start-form-autocomplete.md) templates which allow [customizing](adm-global-autocomplete-templates.md) _all_ autocomplete lists to choose which fields are used for display and searching in v8.
## Features dropped from v7 to v8
### Service bank
The service bank feature has not been ported to AyaNova 8 as it does not appear to be widely used and would need extensive re-working. We could be wrong about this and if the Service Bank feature is important to you please let us know and how you would like to see it implemented as a feature. If there is demand for it we can work it back into AyaNova 8 as a feature based on your feedback.
The service bank feature has not been ported to AyaNova 8 as it does not appear to be widely used and would need extensive re-working. We could be wrong about this so if the Service Bank feature is important to you please let us know and how you would like to see it implemented as a feature. If there is demand for it we can work it back into AyaNova 8 as a feature based on your feedback.