Action log pruning period settings/changes may not take effect in case of a Spotfire server upgrade

Action log pruning period settings/changes may not take effect in case of a Spotfire server upgrade

These issues are seen in cases where user action logging (to database) was enabled in a Spotfire version and post-upgrade of Spotfire server there may be chances if you miss upgrading action log database.
Because, whenever we upgrade the Spotfire server, it affects the connection to the database, database scripts, and the user action logging Upgrade the action log database if it has not been done.
Example:- 
In Spotfire server 7.11 LTS action logging is enabled and the pruning period is set to 720 Hrs (30 Days).
After upgrading Spotfire server from 7.11 LTS to 10.3 LTS, if pruning period is changed, e.g: 720 hrs (30 Days) to 8760 Hrs (1 Year), however, the action logging  database does not capture additional hours.
One possible reason could be the action logging database was not upgraded at the time of the Spotfire server upgrade.

Hence, upgrade the action log database after the Spotfire server upgrade is successful and complete.
Refer the manual links for detailed information about the Action log database upgrade for MSSQL and ORACLE databases. https://docs.tibco.com/pub/spotfire_server/10.3.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-37403F50-95B8-4E78-A423-40D4388F5CA6.html
https://docs.tibco.com/pub/spotfire_server/10.3.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-AB0A47F2-BD7A-4935-9126-44912A8358AE.html
https://docs.tibco.com/pub/spotfire_server/10.3.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-D48D84AF-A95F-4A78-9864-0157D1AF1359.html