Objective
We aim to anticipate all situations so you do not encounter any inconsistencies; however, there may be some impacts on your platform that require attention at the time of the update.
The objective of this checklist is to describe which items are relevant to observe so that the update occurs smoothly in your company.
Checklist Items
See below the items that deserve attention before updating your platform to Voyager (2.0).
Updating to Voyager (2.0)
To apply Voyager (2.0), your platform needs to be on update 1.8.2. If your environment is on a lower update, first update it to the latest package of 1.8.2 (at least 1.8.2-250722) and only then apply the 2.0 update. Check out some useful links: Platform Installation Guide, Platform Update Guide, Installation and Update.
MySQL Database
If you use the MySQL database, it is required to be on version 8.0 to apply the Voyager (2.0) update to your platform. If you need to upgrade your database to MySQL version 8.0, we recommend consulting a database specialist due to the complexity of the procedures. Get more details at: MySQL Database Configuration.
Change of Configuration File
Starting from the Voyager (2.0) update, the platform configuration file will no longer be domain.xml and will become standalone.xml. This item is for information purposes only; no action is required since the system will automatically convert the configurations to standalone.xml when updating the platform.
Change of server.log File Location
Starting from the Voyager (2.0) update, the server.log file will be stored in [installation_directory]\appserver\standalone\log. This item is for information purposes only; no action is required.
Change of Temporary Folders Location
Starting from the Voyager (2.0) update, the temporary folders will be stored in [installation_directory]\appserver\standalone. This item is for information purposes only; no action is required.
Artificial Intelligence (AI) and Net Promoter Score (NPS) Features
For the correct functioning of the features that use Artificial Intelligence (AI) and Net Promoter Score (NPS), you need to allow HTTPS access to the address https://api-fluig.totvs.app in your network infrastructure. Get more details at: Ports and Addresses.
Main Front-end Changes for Voyager (2.0)
We recommend reading the material Main Front-end Changes - Fluig Voyager (2.0) which outlines the impacts on the platform focusing on library modernization, loading optimization, path reorganization, and the introduction of new features such as helper classes, CSS variables, and dark mode in the responsive theme.
Important!
We recommend backing up the database and the installation of TOTVS Fluig before applying the update.
Check the Fluig Application Backup Guide and the Fluig Update Guide for more details.
Tip!
Refer to our documentation on Portability Matrix and Sizing for more information about TOTVS Fluig requirements and performance.