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 c1bfe4c4..99442db4 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,9 +8,9 @@ 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 +## Migrating from AyaNova versions older than 7.6 -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. +To migrate to AyaNova 8 from versions of AyaNova older than AyaNova 7.6 the process is to upgrade in two steps: Upgrade to AyaNova 7.6 first then migrate the data to AyaNova 8. [Contact our support department](https://contact.ayanova.com/contact) for the resources and instructions required. @@ -63,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: @@ -84,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 @@ -109,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. @@ -120,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 @@ -129,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. @@ -148,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 @@ -212,6 +212,20 @@ If a work order in v7 has it's Service Completed checkbox checked but is not Clo The original status in v7 is preserved in v8 as v8 status are now a collection rather than a single item so clicking on status will show the original v7 status. +### Report templates + +AyaNova 7.x report templates are _not_ compatible in any way with AyaNova 8 report templates and can not be migrated automatically. + +The most common reason people have modified AyaNova 7 report templates was to add their logo, that is now [handled automatically](adm-global-logo.md) for you in AyaNova 8 so there may not be a need to customize reports. + +Report templates in AyaNova can 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](https://contact.ayanova.com/contact) AyaNova support for details. + ## What you need to do after migration ### View the migration log @@ -235,10 +249,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. @@ -254,7 +268,7 @@ If you had previously been using a customized Locale in v7 read the important no ### Re-create report templates -If you have any customized report templates they will need to be re-created or re-customized in AyaNova 8. If your only customization was related to logos you may find they will just work in AyaNova 8 without any customization so be sure to set your logo if it hasn't been set already. +See above: [Report template migration](#report-templates). ### RI / WBI Client access settings diff --git a/docs/8.0/ayanova/docs/changelog.md b/docs/8.0/ayanova/docs/changelog.md index 8f833607..82f4a8fc 100644 --- a/docs/8.0/ayanova/docs/changelog.md +++ b/docs/8.0/ayanova/docs/changelog.md @@ -8,6 +8,14 @@ See the [upgrade instructions](ops-upgrade.md) section of this manual for detail ## 2022 +### v8-migrate 8.0.5 (2022-12-30) + +#### Added + +- v8-migrate: workaround to assigned document file migration, now logs and skips without intervention when issues with URI +- v8-migrate: workaround to handle migrating work order item parts from pre 7.6 AyaNova with inventory off but had been on and empty warehouse id set +- Documentation: improved sections regarding migration from v7 to v8 + ### AyaNova 8.0.29 (2022-12-20) #### Fixed diff --git a/docs/8.0/ayanova/docs/ops-import-v7.md b/docs/8.0/ayanova/docs/ops-import-v7.md index 76e055e5..96ee3527 100644 --- a/docs/8.0/ayanova/docs/ops-import-v7.md +++ b/docs/8.0/ayanova/docs/ops-import-v7.md @@ -20,11 +20,35 @@ 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. +AyaNova 7.6 can automatically upgrade any older version of AyaNova newer than AyaNova CE. + 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. +[Contact our support department](https://contact.ayanova.com/contact) for the resources 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. +**WARNING** + +If you are running a version of AyaNova _older than 7.6_ in production use and are not licensed or able to upgrade it to the latest AyaNova 7.6 release, there is an extra step and precaution: you should take care to _NOT_ accidentally upgrade your current, in-production AyaNova installation database but rather a copy of it only, unless you are able to upgrade your production AyaNova to the latest release (have a active support and updates subscription) OR are ready to completely abandon using your older production use AyaNova entirely and permanently. + +This is because AyaNova 7.6 will **automatically** upgrade an older AyaNova database when it is opened and break access to it from the older pre-7.6 AyaNova installations on other computers if they are sharing that database. + +If you were to use a _temporary_ AyaNova 7.6 key issued to you for migration purposes it would expire and prevent access to AyaNova 7.6 so if you were to upgrade your production in-use 7.0.3 for all users it would stop working when the temporary 7.6 key expires. + +This may or may not be an issue for you if you have already thoroughly tested out 8.x and are confident you are ready to completely switch over to it but if you aren't then the upgrade should be done on a computer or virtual machine isolated from the in-production AyaNova you are currently using. + +Assuming you want to take the safest route and not break existing access to the old in-production AyaNova for the time being then: + +The process would be to start with a completely separate computer with access to the AyaNova 8 server but not running your current production AyaNova. + +- Download and install the latest AyaNova 7.6 trial version fresh from our website here (https://ayanova.com/download.htm)[https://ayanova.com/download.htm] +- set it up to use a freshly backed up and restored _copy_ of your in production older AyaNova data +- Once you have configured the latest AyaNova 7.6 to connect to the local _copy_ of your older AyaNova data it will see there isn't a valid license and prompt you for one +- Install the _temporary_ AyaNova 7.6 key [requested from support](https://contact.ayanova.com/contact) earlier using the fetch address and fetch code provided by Support +- Once you have an isolated AyaNova 7.6 running with your data you can continue to follow the migration steps below + +#### Migrating from 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 @@ -34,6 +58,16 @@ Ideally all on the same computer if possible. Speed issues are most noticeable in cases where there are a large number of > 1mb sized Assigned docs or Wiki files that need to be transported across the internet or slow LAN connections. +### Errors during migration + +It is our goal for migration to happen as automatically as possible with as little human intervention as necessary. + +It's possible for older AyaNova 7 data to have one or more issues that the migration utility has not come across previously and been coded to work around triggering an error and stopping migration. + +If this happens please copy and paste the **entire** migration log (not just the error) using the "Copy log to clipboard" button in the v8-migrate utility and send it to AyaNova support. + +They will advise if it's something that can be easily corrected at your end by making a small change in AyaNova 7 or they will forward the log to our Development department to add a work around in the v8-migrate code to enable migration to complete without intervention. + ### Plan for one or more test migrations AyaNova 8 is [different from prior versions](ay-start-changes-from-v7.md) and we recommend doing one or more test migrations before scheduling with your staff to do the final switch-over. @@ -52,11 +86,11 @@ Be sure to have all staff carefully test all business processes they require in The V8Migrate plugin will erase **all** user entered data including attached files in the AyaNova 8 database as the first step with the following exceptions: -- Global settings -- Operations backup settings -- Operations notification settings -- Business logos -- Reports (any missing stock report templates will be re-installed) +- Global settings +- Operations backup settings +- Operations notification settings +- Business logos +- Reports (any missing stock report templates will be re-installed) There is no ability to synchronize or partially migrate only recent changes from v7; the migrate process entirely replaces the V8 data each time it's run. @@ -66,9 +100,11 @@ In other words you cannot continue to work in both AyaNova 7 and AyaNova 8 at th ### Migrating Assigned docs and Wiki files -In AyaNova 7 there were two ways to link to files from within objects: As Wiki files which are stored inside the database and Assigned docs which are file URL links to file system locations visible to all users of AyaNova 7. +Migrating files can have implications that need to be taken into account depending on the size of individual files and all files together as a whole. -In AyaNova 8 all files are stored as "Attachments" in a special file system location controlled by the AyaNova 8 server. +In AyaNova 7 there were two ways to link to files from within objects: As Wiki files which are stored inside the database and Assigned docs which are file URL links to file system locations visible to all users of AyaNova 7 on your network. + +In AyaNova 8 it's much simpler: all files are stored as "Attachments" in a special file system location controlled by the AyaNova 8 server. During migration you have the option of migrating Assigned docs or not however Wiki files will be automatically migrated. @@ -82,6 +118,18 @@ Timeout: there is a built in timeout of 100 seconds for any single operation dur In the case of very large problematic files it may be necessary to have the Users split the file into smaller chunks where possible if it absolutely has to be stored in AyaNova. +#### Viewing the files in database in AyaNova 7 + +In AyaNova 7 you can view the files you have stored in the database ("Embedded" Wiki files) using the [Administration -> Files in database](https://ayanova.com/AyaNova7webHelp/index.html?files_in_database.htm) feature. + +There is no practical way to view how many Assigned docs will be potentially migrated unless they were assigned in the first place from known locations available to all users on the network in which case you may be able to examine the total file storage in the folders used. + +### Migrating to a hosted subscription server + +There is a hard limit by default of 20gb total storage for a subscription service server (unless arrangements have been made for extra storage in advance). Keep this in mind when migrating your AyaNova 7 data to a hosted AyaNova 8 server if you have a large number of assigned docs or Wiki files to be migrated. + +See [above](#migrating-assigned-docs-and-wiki-files) for more details. + ### Avoid corrupted data #### Other users @@ -154,16 +202,16 @@ Do not login to AyaNova 8 until migration has completed or stopped due to error ## Running the migration -- Avoid future problems: If you haven't already, read _all_ of this document before proceeding -- Multi-user only: If migrating from a networked multi-user AyaNova 7.6+ installation, now is the time to ensure all users are out and networked Generator service is stopped. **Do not proceed until this is verified or the data may be corrupted** -- Login to AyaNova 7.6+ as _the_ Administrator / manager account, it's required to be this exact account, not another one -- Select the "V8 Migrate" plugin in AyaNova 7 from the main window plugin menu and the login and server URL dialog will open -- Enter the URL of your AyaNova 8 server. The easiest way to get this is to simply copy the entire URL displayed in the browser from the AyaNova 8 web application web page, for example the login page. -- 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. -- 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. +- Avoid future problems: If you haven't already, read _all_ of this document before proceeding +- Multi-user only: If migrating from a networked multi-user AyaNova 7.6+ installation, now is the time to ensure all users are out and networked Generator service is stopped. **Do not proceed until this is verified or the data may be corrupted** +- Login to AyaNova 7.6+ as _the_ Administrator / manager account, it's required to be this exact account, not another one +- Select the "V8 Migrate" plugin in AyaNova 7 from the main window plugin menu and the login and server URL dialog will open +- Enter the URL of your AyaNova 8 server. The easiest way to get this is to simply copy the entire URL displayed in the browser from the AyaNova 8 web application web page, for example the login page. +- 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. +- 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/mkdocs.yml b/docs/8.0/ayanova/mkdocs.yml index c1aa23f0..c82eab69 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-12-20 +copyright: Copyright © 2022 Ground Zero Tech-Works Inc. REV-2022-12-30 extra: generator: false # Extensions