FAS 7.0 Upgrade Notes

FAS 7.0 is an incremental step from FAS 6.5, with many improvements, mainly in the backend (indexing, query execution).

There are no frontend changes in FAS 7.0 compared to FAS 6.5.

Attribute Name Localisations

FAS 7.0 changes how attribute name localisations are stored and loaded from config/i18n/localization.*.xml: the names and formats for attributes must be configured only in the localisation file for the universe that contains the attribute type, configurations in other files are silently ignored. Previous versions saved the configurations in all files and loaded the configuration in an arbitrary order, leading to 'lost attribute type names'. See FAS-1520 for additional details.

These changes require manual edits to the configuration files stored in config/i18n. Alternatively, you can also re-enter all attribute name localisations using the BM.

For manual editing, follow these steps before starting the qserver:

1. determine the lists of primary and secondary attribute types in the data
2. collect all <attribute-type> configurations from config/i18n/localzation.*.xml
3. for every universe and locale:
   1. open config/i18n/localization.UNIVERSE.LOCALE.xml in a text editor
   2. remove all <attribute-type> elements.
   3. add all <attribute-type> elements for this universe and locale

Editing of Configuration Files
The configuration files are required for FAS to work properly, and errors when editing can lead to problems when starting any FAS process.

Always make a backup before editing a configuration file, and only change the elements you need to change. In particular, do not reformat the files.

Trigger Types

FAS 6.5 no longer knows about 'end user types' (System Manager > Management > User Types). In FAS 6.5, we migrated the end-user-types to a new fh_usertype trigger type.

FAS 7.0 removed this trigger type from the set of internal trigger types. If the user type functionality is needed, the user must define a trigger type (FAS-6271).

Reporting

FAS 7.0 removed the support for running Fredhopper Reporting. The Business Manager will be able to display existing reports.