BUSINESS ADMINISTRATION IMPORT FROM V7

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

What is imported and where

All objects

All imported business objects will be tagged with "v7-import" to easily identify them. There is no need to keep this tag if you wish to remove it, it's for informational purposes only.

Most objects

Most object will retain their name and will be imported directly with the following exceptions:

Global Wiki

v8 will 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".

Region Wiki

v8 will 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"

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.

For details see the Authorization roles guide for more information.

Clients

v7 Clients have been renamed to "Customers"

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.

Wiki embedded files

In V8 Wiki embedded files are now Attachments 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

Wiki pages

Wiki 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:
- 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 exported to new attachments feature)

Users

Users are imported 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"

What you need to do after importing

Setup users

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

4.9 KiB Raw Blame History