From 1e683a0d4529570d571d540016c07e4441cb884f Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 16 Nov 2022 16:54:42 +0000 Subject: [PATCH] --- .../ayanova/docs/ay-biz-admin-migrate-v7.md | 100 ++++++++++-------- docs/8.0/ayanova/docs/ops-import-v7.md | 12 ++- .../ayanova/docs/tour-bootstrap-evaluate.md | 18 +++- docs/8.0/ayanova/mkdocs.yml | 2 +- 4 files changed, 78 insertions(+), 54 deletions(-) diff --git a/docs/8.0/ayanova/docs/ay-biz-admin-migrate-v7.md b/docs/8.0/ayanova/docs/ay-biz-admin-migrate-v7.md index 251e00dc..c1bfe4c4 100644 --- a/docs/8.0/ayanova/docs/ay-biz-admin-migrate-v7.md +++ b/docs/8.0/ayanova/docs/ay-biz-admin-migrate-v7.md @@ -8,6 +8,12 @@ For a technical guide to migration process see the [Operations migrate guide](op For a guide to the feature changes from AyaNova 7 see the [Changes from AyaNova 7 guide](ay-start-changes-from-v7.md). +## Migrating from AyaNova versions older than 7 + +To migrate to AyaNova 8 from versions of AyaNova older than AyaNova 7 the process is to upgrade in two steps: Upgrade to AyaNova 7 first then migrate the data to AyaNova 8. + +[Contact our support department](https://contact.ayanova.com/contact) for the resources and instructions required. + ## Plan the migration The migration should be planned and tested in advance and involve all staff who use AyaNova to ensure the minimum possible disruption to the business. @@ -57,19 +63,19 @@ The Region Wiki if found will be migrated to a User account created just to hold ### Security groups -- Security groups have been replaced by Roles. -- No v7 security group information or settings are migrated into v8. -- v7 migrated Users will automatically be set to No Role in order to protect information security; the business administrator will need to set each user to the most appropriate new roles after migrated is completed. +- Security groups have been replaced by Roles. +- No v7 security group information or settings are migrated into v8. +- v7 migrated Users will automatically be set to No Role in order to protect information security; the business administrator will need to set each user to the most appropriate new roles after migrated is completed. For details see the [Authorization roles](ay-biz-admin-roles.md) guide for more information. ### Clients -- v7 Clients have been renamed to "Customers" +- v7 Clients have been renamed to "Customers" ### Parts -- In v7 Parts had Part number and Part Name fields. Part Number was always intended as the _primary_ identifier for a part however in v8 we've changed Parts to use the more consistent Part Name as the _primary_ identifier. Users should use the Part Name field in v8 as the primary and sole identifier for a Part wherever possible. This field like all v8 name fields has no practical length limit and should be the main field used to identify parts both internally and externally. +- In v7 Parts had Part number and Part Name fields. Part Number was always intended as the _primary_ identifier for a part however in v8 we've changed Parts to use the more consistent Part Name as the _primary_ identifier. Users should use the Part Name field in v8 as the primary and sole identifier for a Part wherever possible. This field like all v8 name fields has no practical length limit and should be the main field used to identify parts both internally and externally. In order to accomodate this change, the V8 migration utility offers two ways to migrate the existing part fields as an optional choice before migration: @@ -78,7 +84,7 @@ In order to accomodate this change, the V8 migration utility offers two ways to ### Unit Models -- In v8 Unit Models no longer have the "Model Number" field. The "Name" field is now the primary identifier. Migrated v7 Unit Models will have their Model Number and Name fields combined into the single v8 Name field. +- In v8 Unit Models no longer have the "Model Number" field. The "Name" field is now the primary identifier. Migrated v7 Unit Models will have their Model Number and Name fields combined into the single v8 Name field. ### Schedule markers @@ -103,8 +109,8 @@ Reminders do not have a Completed checkbox so that property is not migrated howe ### Localized Text / Translation -- In V8 Localized text has been renamed to "Translation". -- V7 Localized text will only be migrated if it has been customized. Any customized Locales will be migrated to the best guess of source language into AyaNova 8. It tries to make a best guess as to which language each user was using but if it can't tell it defaults to the English based translation. You can adjust this after migrate for the users or they can set it themselves and you can delete any un-needed translations. +- In V8 Localized text has been renamed to "Translation". +- V7 Localized text will only be migrated if it has been customized. Any customized Locales will be migrated to the best guess of source language into AyaNova 8. It tries to make a best guess as to which language each user was using but if it can't tell it defaults to the English based translation. You can adjust this after migrate for the users or they can set it themselves and you can delete any un-needed translations. **IMPORTANT NOTE ABOUT MIGRATED TRANSLATIONS** V8Migrate will migrate customized translations from v7 and set the migrated Users to that same translation, however, we **strongly recommend** that you do not actually use the migrated translation once familiar with where everything you need appears in v8 but rather replicate any custom translation changes required in one of the stock V8 translations to avoid confusion as several objects have been renamed for clarity. @@ -114,8 +120,8 @@ This will avoid issues with documentation and some areas of the UI being in conf ### Wiki embedded files -- In V8 Wiki embedded files are now [Attachments](ay-start-form-attachments.md) and are separate from the Wiki page. -- In v7 only a limited set of objects could have Wiki pages and embedded files, now, all business objects support Attachments +- In V8 Wiki embedded files are now [Attachments](ay-start-form-attachments.md) and are separate from the Wiki page. +- In v7 only a limited set of objects could have Wiki pages and embedded files, now, all business objects support Attachments ### Tags @@ -123,18 +129,18 @@ This will avoid issues with documentation and some areas of the UI being in conf The following objects from v7 will be migrated as tags in v8: -- User certification -- User skill -- Client group -- Dispatch zone -- Part category -- Regions -- Scheduleable user group -- Unit service type -- Unit model category -- Vendor type -- 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 +- Vendor type +- Work order category +- Work order item type Objects migrated to v8 will automatically be tagged with the corresponding tag that replaces the above feature. @@ -142,32 +148,32 @@ Objects migrated to v8 will automatically be tagged with the corresponding tag t [Wiki](ay-start-form-wiki.md) pages have change substantially in v8 based on user feedback. -- In v7 only a limited set of objects could have Wiki pages and embedded files, now, all business objects support Wiki pages -- The migrate process will by necessity need to discard some unsupported formatting elements from the v7 format wiki pages. -- Things that will be lost in the migration process are: - - Colors - - Font sizes - - Font faces (i.e. "Arial", "Courier" etc) - - Text alignment (left, center, right) - - internal AyaNova links to objects (for example linking directly to a Client record inside a wiki page) -- Things that will be kept: - - All entered text - - Lists - - Bolded text - - Underlined text - - Italicized text - - Images - - External URL links - - Wiki embedded files (will be migrated to new attachments feature) +- In v7 only a limited set of objects could have Wiki pages and embedded files, now, all business objects support Wiki pages +- The migrate process will by necessity need to discard some unsupported formatting elements from the v7 format wiki pages. +- Things that will be lost in the migration process are: + - Colors + - Font sizes + - Font faces (i.e. "Arial", "Courier" etc) + - Text alignment (left, center, right) + - internal AyaNova links to objects (for example linking directly to a Client record inside a wiki page) +- Things that will be kept: + - All entered text + - Lists + - Bolded text + - Underlined text + - Italicized text + - Images + - External URL links + - Wiki embedded files (will be migrated to new attachments feature) ### Users Users are migrated directly with the following exceptions: -- Security group, now Role, see above -- Login credentials and password are not migrated and will need to be set -- Active status is set to false on all migrated users except the Adminstrator account -- Administrator account password is not migrated, instead the new v8 SuperUser account replaces it and defaults to login "superuser" and password "l3tm3in" +- Security group, now Role, see above +- Login credentials and password are not migrated and will need to be set +- Active status is set to false on all migrated users except the Adminstrator account +- Administrator account password is not migrated, instead the new v8 SuperUser account replaces it and defaults to login "superuser" and password "l3tm3in" ### Service bank @@ -229,10 +235,10 @@ Note: **Inactive users do not display in the v8 schedule** - in v8 the schedule All active users will need to have some settings made: -- Role - you will need to select one or more Authorization Roles to grant the User access to AyaNova. -- Login and Password - These are not migratable and need to be set for the user to log in, they can change their login and password themselves once they log in. -- Translation - The migration process will make a guess as to the most appropriate translation but you may need to adjust this setting -- Active - users are migrated as Inactive and must be set to Active +- Role - you will need to select one or more Authorization Roles to grant the User access to AyaNova. +- Login and Password - These are not migratable and need to be set for the user to log in, they can change their login and password themselves once they log in. +- Translation - The migration process will make a guess as to the most appropriate translation but you may need to adjust this setting +- Active - users are migrated as Inactive and must be set to Active Once Users are able to login they will need to subscribe to any [Notifications](home-notify-subscriptions.md) they require. The V8 Notification system is simplified from v7 and easier to set up but it can't be migrated as they are very different systems. diff --git a/docs/8.0/ayanova/docs/ops-import-v7.md b/docs/8.0/ayanova/docs/ops-import-v7.md index fa6e44aa..76e055e5 100644 --- a/docs/8.0/ayanova/docs/ops-import-v7.md +++ b/docs/8.0/ayanova/docs/ops-import-v7.md @@ -16,7 +16,15 @@ If you can login to the AyaNova 8 server from a computer running AyaNova 7, you ### Migrating from ayanova 7.6 patch 7 or older -The V8Migrate plugin can migrate data from AyaNova 7.6 patch 8 or newer ONLY. For versions of AyaNova older than 7.6 patch 8 you must first upgrade them before continuing. +The V8Migrate plugin can migrate data from AyaNova 7.6 patch 8 or newer ONLY. + +To migrate to AyaNova 8 from versions of AyaNova older than AyaNova 7.6 patch 8 (i.e. AyaNova 1.x, 2.x, 3.x, 4.x, 5.x, 6.x, 7.x older versions) the process is to upgrade in two steps: Upgrade to AyaNova 7.6 latest release first then migrate the data to AyaNova 8. + +We will provide a temporary license key and instructions at no charge to enable you to migrate any older version of AyaNova to AyaNova 8. + +[Contact our support department](https://contact.ayanova.com/contact) for the resources and instructions required. + +AyaNova CE: it's potentially possible to upgrade to AyaNova 8 from AyaNova CE in a triple step upgrade process but we would need to do it in-house, contact AyaNova support for details. ### How to get the fastest possible migration @@ -154,7 +162,7 @@ Do not login to AyaNova 8 until migration has completed or stopped due to error - There is a "Test URL" button to confirm if you have entered the correct address or not. - Enter your AyaNova 8 SuperUser account login credentials. No other account is permitted to perform this operation. The default SuperUser account login name is "superuser" and password is "l3tm3in" if it has not been changed. - A **Migration log** form will popup and show the progress of the Migration operation including any errors or specific action required for your particular data. -- Do **NOT** login to the AyaNova 8 server while migration is taking place, it will crash the migration completely. +- Do **NOT** login to the AyaNova 8 server while migration is taking place, it will crash the migration completely. - There is no easy way to estimate how long migration will take which is why several test migrations should be done before the final migration. Time of migration depends on the network latency and speed between the V8 Migrate plugin and the AyaNova 8 server as well as the number and complexity of objects entered into AyaNova and the quantity and size of files that may need to be uploaded. ## After the migration diff --git a/docs/8.0/ayanova/docs/tour-bootstrap-evaluate.md b/docs/8.0/ayanova/docs/tour-bootstrap-evaluate.md index f638c5d3..5ee61ca9 100644 --- a/docs/8.0/ayanova/docs/tour-bootstrap-evaluate.md +++ b/docs/8.0/ayanova/docs/tour-bootstrap-evaluate.md @@ -146,17 +146,27 @@ Once you have access to AyaNova and some sample data generated to play with we r We have several guided tours in the Business admin section about customization including [adding custom fields to forms](tour-bizadmin-form-custom-fields.md), [hiding un-needed form fields](tour-bizadmin-form-remove-fields.md), [changing the displayed text](tour-bizadmin-form-custom-translation.md) and more. - In addition all the Report templates in AyaNova can be customized and new ones created using the built in [report template editor](ay-report-edit.md). + Report templates in AyaNova can also be customized and new ones created using the built in [report template editor](ay-report-edit.md). + We recommend looking through the reports you might use in your business and [make or plan for any changes](adm-report-templates.md#how-to-modify-report-templates) required if the stock report templates don't meet your needs as they are. We suggest making a duplicate copy of any stock report templates you want to modify first and then working with the duplicate so that you always have the original for reference. If you prefer to have report templates modified or created for you, we may be able to provide that service for a fee, contact AyaNova support for details and a quotation. Be **careful** not to customize too much too early in the evaluation process; be sure you and your potential staff who would be using AyaNova have a basic familiarity with AyaNova's stock forms and features first before customizing. If you start renaming fields or dropping them (for example) it can be hard to match up what is written in the documentation with what they are seeing in the program. It's possible to customize and remove entire sections of the Work order form (for example) but it may turn out that some of those would be useful so it's best to get a good idea what's in there before making too many changes early on. -8. Importing exsting data - often a company starting out with AyaNova will want to import existing data to save time. If this is something you may need to do, AyaNova has a built in [import feature](adm-import.md) which enables you to import data from text files which you should definitely try out with real data as part of your evaluation process. +8. Importing exsting data - often a company starting out with AyaNova will want to import existing data to save time. - Note that we do _not_ recommend importing data early in the evaluation process but rather we recommend using the generated sample data for early evaluation instead because the generated data is intended to appear as if it was real world data created by a service company over time so it's often more helpful for evaluation purposes as the data is more realistic and is used in multiple areas giving Users a chance to see how it all links together. + **Before you import** + We recommend importing data as part of the evaluation process but **not too soon**: we recommend using the generated sample data for early evaluation instead because the generated data simulates real world data created by a service company over time so it's often more helpful for evaluation purposes as the data is more realistic and is used in multiple areas giving Users a chance to see how it all links together. + **Importing from other programs** + AyaNova has a built in [import feature](adm-import.md) which enables you to import data from text files which you should try out with real data as part of your evaluation process. + + **Importing from QuickBooks** If you use QuickBooks desktop edition you can import data directly from QuickBooks using our [QBI QuickBooks integration utility](integration-qbd) (more accounting integrations are in the works, contact us if there is a specific one of interest, we may already be working on it). - If you are using an older version of AyaNova we have a [migration utility](ay-biz-admin-migrate-v7.md) that will import legacy AyaNova data to this latest version. + + **Importing from older versions of AyaNova** + If you are using an older version of AyaNova we have a [migration utility](ay-biz-admin-migrate-v7.md) that will **import legacy AyaNova data** to version 8. + + Note that Report Templates are not automatically migrated from older versions of AyaNova so they will need to be recreated if you have any customization more complex than putting your logo on reports (which is built in to stock report templates in AyaNova 8). 9. Decision - is everyone comfortable with AyaNova? Has everyone tried out the features they will be using in production? Are there any lingering questions that need to be answered? Now is the time to be certain and if necessary go back and confirm anything before moving to the next step. diff --git a/docs/8.0/ayanova/mkdocs.yml b/docs/8.0/ayanova/mkdocs.yml index f6913937..fdfb3c81 100644 --- a/docs/8.0/ayanova/mkdocs.yml +++ b/docs/8.0/ayanova/mkdocs.yml @@ -7,7 +7,7 @@ theme: site_name: AyaNova manual site_dir: '../../../server/AyaNova/wwwroot/docs' strict: true -copyright: Copyright © 2022 Ground Zero Tech-Works Inc. REV-2022-11-14 +copyright: Copyright © 2022 Ground Zero Tech-Works Inc. REV-2022-11-16 extra: generator: false # Extensions