BPM Hotfixes may include Openspace updates -- effectively a new version of the Openspace webapp. When BPM Hotfix is applied (via TCT), the new Openspace is deployed, including default configuration files.
If you have customized the existing Openspace (e.g. for SSO and/or disabling unused locales), you will need to re-apply the changes after applying the hotfix.
Environment
Any supported AMX/BPM system
Resolution
Re-applying customizations will be easier if you make external copies of any modified files prior to applying the BPM Hotfix. It is recommended to compare/merge your customized files with the new defaults - just in case the HF introduced some new properties or default values.
Backing up Openspace Customizations - 4.0, 4.1, 4.2
BPM Hotfixes which include Openspace updates will revert to default configuration.
Backup any customizations (e.g. config.properties, locale.properties) before applying Hotfixes!