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
2021-08-31 19:54:11 +00:00
parent 682dd73a44
commit 35f84b7bb8
3 changed files with 89 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
docs/8.0/ayanova/docs/ay-biz-admin-import-v7.md
View File

@@ -1,30 +1,30 @@
# BUSINESS ADMINISTRATION IMPORT FROM V7
# BUSINESS ADMINISTRATION MIGRATE TO V8
## OVERVIEW
This page outlines the import changes and setup tasks that will need to be done after import from a business administration point of view.
For a technical guide to import see the [Operations import guide](ops-import-v7.md)
This page outlines the changes and setup tasks that will need to be done after migration from a business administration point of view.
For a technical guide to migration process see the [Operations migrate guide](ops-import-v7.md)
## What is imported and where
## What is migrated and where
### All objects
All imported business objects can be tagged to easily identify them. By default it will tag all imported objects with "v7-import" or you can clear this field and leave it blank if you do not wish to have all the migrated items tagged. This tag is provided so there is a record of which items were migrated and which were created after migration however there is no technical requirement for this tag; it's for informational and troubleshooting purposes only.
All migrated business objects can be tagged to easily identify them. By default it will tag all migrated objects with "v8-migrate" or you can clear this field and leave it blank if you do not wish to have all the migrated items tagged. This tag is provided so there is a record of which items were migrated and which were created after migration however there is no technical requirement for this tag; it's for informational and troubleshooting purposes only.
### Most objects
Most object will retain their name and will be imported directly with the following exceptions:
Most object will retain their name and will be migrated directly with the following exceptions:
### Global Wiki
v8 does not have a Global Wiki page (the Wiki page formerly accessible from the opening screen in AyaNova 7), the export will move the Wiki and any embedded files to a User account created just to contain it's Wiki and attached files named "V7_EXPORT_GLOBAL_REPOSITORY".
v8 does not have a Global Wiki page (the Wiki page formerly accessible from the opening screen in AyaNova 7), the migration will move the Wiki and any embedded files to a User account created just to contain it's Wiki and attached files named "V8_MIGRATE_GLOBAL_REPOSITORY".
### Region Wiki
v8 does not have Regions, all functionality previously in Regions will be split out into several new and changed objects.
The Region Wiki if found will be exported to a User account created just to hold the Wiki and files named ""V7_REGION_WIKI_REPOSITORY_region name"
The Region Wiki if found will be migrated to a User account created just to hold the Wiki and files named ""V8_MIGRATE_REGION_WIKI_REPOSITORY_region name"
### Security groups
* Security groups have been replaced by Roles.
* No v7 security group information or settings are imported into v8.
* v7 imported 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 import is completed.
* 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.
@@ -33,7 +33,7 @@ For details see the [Authorization roles](ay-biz-admin-roles.md) guide for more
### Localized Text
* In V8 Localized text has been renamed to "Translation".
* V7 Localized text will only be imported if it has been customized. Any customized Locales will be exported 4 times: once for each base language that comes with AyaNova 8. This is because the export needs to merge the v7 translations into v8 and cannot reliably know which language the original v7 translation was based upon. 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 export for the users or they can set it themselves and you can delete any un-needed translations.
* 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.
### Wiki embedded files
* In V8 Wiki embedded files are now [Attachments](ay-start-form-attachments.md) and are separate from the Wiki page.
@@ -42,7 +42,7 @@ For details see the [Authorization roles](ay-biz-admin-roles.md) guide for more
### Tags
[Tags](ay-start-form-tags.md) are a new feature for AyaNova 8 that replace and improve upon several different categorization features in v7.
The following objects from v7 will be imported as tags in v8:
The following objects from v7 will be migrated as tags in v8:
* User certification
* User skill
* Client group
@@ -56,14 +56,14 @@ The following objects from v7 will be imported as tags in v8:
* Work order category
* Work order item type
Objects imported to v8 will automatically be tagged with the corresponding tag that replaces the above feature.
Objects migrated to v8 will automatically be tagged with the corresponding tag that replaces the above feature.
### Wiki pages
[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 import process will by necessity need to discard some unsupported formatting elements from the v7 format wiki pages.
* Things that will be lost in the export process are:
* 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)
@@ -77,25 +77,41 @@ Objects imported to v8 will automatically be tagged with the corresponding tag t
* Italicized text
* Images
* External URL links
* Wiki embedded files (will be exported to new attachments feature)
* Wiki embedded files (will be migrated to new attachments feature)
### Users
Users are imported directly with the following exceptions:
Users are migrated directly with the following exceptions:
* Security group, now Role, see above
* Login credentials and password are not imported and will need to be set
* Active status is set to false on all imported users except the Adminstrator account
* Administrator account password is not imported, instead the new v8 SuperUser account replaces it and defaults to login "superuser" and password "l3tm3in"
* 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
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. No data is migrated from the v7 Service Bank to v8.
## What you need to do after importing
## What you need to do after migration
### View the migration log
A copy of the migration log is automatically sent in AyaNova 8 in a Memo to the SuperUser account and is a mirror copy of the migration log displayed during migration.
This log may contain important instructions and indications of any objects that could not be migrated or will need attention.
Be sure to check this log carefully before proceeding and take any actions recommended.
### Check your data
Ensure that your data has migrated by comparing v7 to v8 objects in both interfaces.
### Setup users
Users are migrated to inactive accounts with no authorization Roles, password or login name set.
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 exportable and need to be set for the user to log in, they can change their login and password once they log in.
* Translation - The export process will make a guess as to the most appropriate translation but you may need to adjust this setting
* Active - users are exported 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
### 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.

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

@@ -164,13 +164,14 @@ The following objects from v7 have been replaced by tags in v8:
In addition, all objects imported from v7 will be tagged with "v7-import".
### Reports
todo: reports, major differences from v7 here
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.
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.
### Wiki
The [Wiki](ay-start-form-wiki.md) feature has been changed substantially based on user feedback.
##### 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.

66
docs/8.0/ayanova/docs/ops-import-v7.md
View File

@@ -1,46 +1,70 @@
## OVERVIEW
This is the technical guide to the export to v8 process.
This is the technical guide to the migration to v8 process.
There is also a business administration focused [guide](ay-biz-admin-import-v7.md) to import outlining business object changes and steps that need to be taken after the export process has completed.
There is also a business administration focused [guide](ay-biz-admin-import-v7.md) to migration outlining business object changes and steps that need to be taken after the migrate process has completed.
Exporting is done with a AyaNova 7 plugin "Export to V8" which is installed automatically with current releases of AyaNova 7.xx or newer.
Migration is done by the AyaNova 7 plugin "V8Migrate" which is available as an optional install from the AyaNova [Download](https://www.ayanova.com/download.htm) page.
The export process happens via network and you can export to any server on the same computer or visible inside or outside your network via HTTP.
The migrate process happens via network and you can migrate to any server on the same computer or visible inside or outside your network via HTTP.
### IMPORTING FROM AyaNova 7.5 OR OLDER
The Export to V8 plugin can export data from AyaNova 7.xx or newer. For versions of AyaNova older than 7.xx you must first upgrade them to 7.xx before continuing.
### 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.
### SPEED
It is recommended where possible that migration be done on the fastest possible network connection between the V8Migrate plugin, the AyaNova 7 database and the AyaNova 8 server. 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.
### MIGRATING ASSIGNED DOCS / 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 arbitrary locations for files visible to all users of AyaNova 7.
In AyaNova 8 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.
AyaNova 8 has a hard limit of 10GiB per attachment. The migration utility will log a warning about any files found to be larger than 10GiB and will not attempt to migrate them.
Note, however that there may also be other limitations depending on how and where the AyaNova 8 server is hosted. For example if the AyaNova 8 server sits behind an nginx proxy server (for example) there is a default limit of 30mb for file uploads which may need to be adjusted. The migration plugin will keep track of any files that fail to migrate due to a 413 file size exceeded error and it will log a warning and will reset the limit down to that level and not attempt to export any files larger than the limits it "finds".
A 1 GiB file can take easily take an hour to migrate to a remotely hosted server via an average internet connection so exporting Assigned docs may need to be undertaken very carefully if the users have linked to a large number of big files in AyaNova 7 and you are migrating to a remote server across the internet.
Timeout: there is a built in timeout of 100 seconds for any single operation during migration, this can be increased in the options dialog of the migration plugin displayed after login to as much as 3600 seconds (1 hour) and if you see timeout errors during migration of large files you will need to increase this value.
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.
### PLAN FOR ONE OR MORE TEST EXPORTS
AyaNova 8 is very different from prior versions and we recommend doing one or more trial exports before scheduling with your staff to do the final switch-over. Plan on taking plenty of time to go through the exported data in AyaNova 8, familiarize yourself and your staff with all the changes in the new version of AyaNova.
AyaNova 8 is very different from prior versions and we recommend doing one or more trial migrations before scheduling with your staff to do the final switch-over. Plan on taking plenty of time to go through the migrated data in AyaNova 8, familiarize yourself and your staff with all the changes in the new version of AyaNova.
Ensure data has exported as expected and that all staff are comfortable with working in the new AyaNova before committing to a final export and switch over.
Ensure data has migrated as expected and that all staff are comfortable with working in the new AyaNova before committing to a final migrate and switch over.
A test export will give you an idea of how long it will take to better plan the final export and change over to v8.
A test migrate will give you an idea of how long it will take to better plan the final migrate and change over to v8.
## WARNINGS
### AyaNova 8 database will be erased
The export plugin will erase all data including attached files in the AyaNova 8 database as the first step.
There is no ability to synchronize or export only recent changes from v7, the export process entirely replaces the V8 data.
The V8Migrate plugin will erase all data including attached files in the AyaNova 8 database as the first step.
Note that it's possible to run the export plugin more than once for testing and evaluation just be aware that you will lose anything entered into V8 each time you run the Export to V8 plugin from v7.
There is no ability to synchronize or migrate only recent changes from v7, the migrate process entirely replaces the V8 data.
In other words you cannot continue to work in both AyaNova 7 and AyaNova 8 at the same time and expect to export and import data repeatedly to keep them in "sync".
Note that it's possible to run the migrate plugin more than once for testing and evaluation just be aware that you will lose anything entered into V8 each time you run the Export to V8 plugin from v7.
In other words you cannot continue to work in both AyaNova 7 and AyaNova 8 at the same time and expect to migrate and import data repeatedly to keep them in "sync".
### Avoid corrupted data
#### Other users
If other users are working in AyaNova when the export plugin is run the resulting export data may be corrupted as there could be records changed or missing that will be required to import. Be certain no other users are working in AyaNova 7 before you export.
If other users are working in AyaNova when the migrate plugin is run the resulting migrate data may be corrupted as there could be records changed or missing that will be required to import. Be certain no other users are working in AyaNova 7 before you migrate.
#### Generator
Be sure to stop the AyaNova Generator *before* starting the export plugin. Failing to do so could result in a corrupted export.
Be sure to stop the AyaNova 7 Generator *before* starting the migrate plugin. Failing to do so could result in a corrupted migration.
#### Remote access users
@@ -48,13 +72,13 @@ Ensure no users are making changes via a remote access option such as the DataPo
### Lost entries
If you have a networked installation of AyaNova 7, when you are ready to transition to the newer version of AyaNova you will need to ensure that no other users are still working in the old AyaNova 7 making entries that will never be brought over to v8 after you do the final export to v8.
If you have a networked installation of AyaNova 7, when you are ready to transition to the newer version of AyaNova you will need to ensure that no other users are still working in the old AyaNova 7 making entries that will never be brought over to v8 after you do the final migrate to v8.
We recommend stopping the V7 database server immediately after the final export if there is any chance that there are still users inside or outside of your network that may access AyaNova 7.
We recommend stopping the V7 database server immediately after the final migrate if there is any chance that there are still users inside or outside of your network that may access AyaNova 7.
### Before uninstalling AyaNova 7
Examine your imported data in AyaNova 8+; carefully ensure that the data you expect to see has been imported properly. You may still need to make another export in case of any issues that arise so it's not a good idea to immediately uninstall AyaNova 7 until you are sure the newer version of AyaNova has all your data in it and is ready for business.
Examine your imported data in AyaNova 8+; carefully ensure that the data you expect to see has been imported properly. You may still need to make another migrate in case of any issues that arise so it's not a good idea to immediately uninstall AyaNova 7 until you are sure the newer version of AyaNova has all your data in it and is ready for business.
We recommend keeping your AyaNova 7 installation for some time on at least one computer after switching to v8 in case an issue comes up or something needs to be checked.
@@ -62,10 +86,10 @@ We recommend keeping your AyaNova 7 installation for some time on at least one c
We recommend you keep one or more backup copis of your AyaNova 7 database in a safe location **OFF SITE** for at least a year after transitioning to AyaNova 8 in case any issues arise. If possible a "permanent" copy burned to DVD may be prudent.
## EXPORTING FROM AYANOVA 7.xx
## MIGRATION FROM AYANOVA 7.xx
* Avoid future problems: If you haven't already, go back and read the section titled "WARNINGS" above carefully.
* Multi-user only: If exporting from a networked multi-user AyaNova 7.xx installation, now is the time to ensure all users are out and networked Generator service is stopped. **Do not proceed until this is verfied**.
* Multi-user only: If migrating from a networked multi-user AyaNova 7.xx installation, now is the time to ensure all users are out and networked Generator service is stopped. **Do not proceed until this is verfied**.
* Login to AyaNova 7.xx as *the* Administrator / manager account
* Select the "Export to V8" plugin in AyaNova 7 from the main window plugin menu and the login and server URL dialog will open (note: this plugin is installed by default in the latest releases of AyaNova. If you don't see it, you may need to upgrade to the latest release first.)
* Enter the URL of your AyaNova 8 server. There is a "Test URL" button to optionally confirm if you have entered the correct address or not.
@@ -73,5 +97,5 @@ We recommend you keep one or more backup copis of your AyaNova 7 database in a s
* A form will popup and show the progress of the Export operation. There is no easy way to estimate how long this will take, it depends on the network latency and speed between the Export to V8 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. Allow plenty of time for this operation.
* When the export is finished you will be able to login to V8 and start [setting things up](ay-biz-admin-import-v7.md)
* When the migrate is finished you will be able to login to V8 and start [setting things up](ay-biz-admin-import-v7.md)