General Upgrade Information
Refer to the information below on the steps you may need to perform before and after the upgrade process.
NOTE: Also review the information up to and including the version to which you are upgrading.
The information below should be reviewed and is not version specific.
Command Execution and User Management Security
A new field "Allow Exec" has been added to the Role form which determines if a user role can invoke the "Exec" Cicode function.
A new field "Manage Users" has been added to the Role form which determines if a user role is authorized to manage user accounts.
RPC server-side security
A new field "Allow RPC" has been added to each of the server forms which determines if a server can accept remote MsgRPC and ServerRPC calls.
Earliest Legacy Version
If you are performing an online upgrade, use the Citect.ini parameter
NOTE: You should reset this parameter to its normal setting when an upgrade is complete.
Setup the Development Environment
The existing version may have project configuration [INI] file settings that are related to the configuration and may be required to compile the project. The specific project configuration settings can be added to the new version using the Computer Setup Editor.
The previous settings can be migrated to the new version by replacing the new configuration [INI] file with the previous version of the INI file. When doing this, the following parameters would then need to be updated / added to reflect the new installation settings in the previous configuration file. Any old settings that are no longer used are removed from the file when the Computer Setup Editor is used to save the file the first time.
. Path: [CtEdit] Bin, [CtEdit] User, [CtEdit] Data, [CtEdit] Log, [CtEdit] Config
These settings should be copied from the new version configuration file (INI) to the current / previous file. The paths need to be set to the product application directories for the new version installation.
MsgRPC and ServerRPC server-side security
A new field "Allow RPC" has been added to the Role form which determines if a user or group of users can perform remote MsgRPC or ServerRPC calls. On upgrading projects this field will be left blank which will raise the following compiler warning message.
'Allow RPC' permission is not defined (defaulting to FALSE)
For existing users can continue to use MsgRPC and ServerRPC, you need to manually change the value of “Allow RPC” to TRUE.
If these functions are used in your project, the roles that execute the functions will also need to have the permissions enabled.