The changes you make to the layout or pane are applied permanently to all RiskVision user accounts and even when the users log in and log out of RiskVision several times. The layout or pane that is customized using the Configure UI permission are preserved and continue to work as expected because the changes are saved directly to the database.
When you modify the UICustomization.xml file present in the %AGILIANCE_HOME%\Tomcat\ webapps\spc\WEB-INF\classes directory, copy the UICustomization.xml file to the %AGILIANCE_ HOME%\config directory to ensure that the upgrade process picks the custom changes.
 | RiskVision strongly recommends customizing the user interface with the Configure UI permission. |
Only the changed <component> XML blocks must be copied in the UICustomization.xml file in the %AGILIANCE_HOME%\config directory. And, remove all unchanged <component> XML blocks. This makes upgrades much easier to do successfully and changes are easy to track down and update when needed.
Also, when RiskVision server is updated, the changes to the UICustomization.xml file need to be updated to match any UI changes in the newer version of RiskVision server by comparing with the new UICustomization.xml file of the %AGILIANCE_HOME%\Tomcat\webapps\spc\WEB-INF\classes directory. Using an old UICustomization.xml file with a new RiskVision server version might cause problems, such as hiding new features in the UI. As a reason, the UICustomization.xml file is versioned and will be rejected if the version in the file header doesn't match.
However, if you configure the UI using the Configure UI feature in the UI, this is automatically handled by tracking the "changes" that were made and reapplying them to the new UI of the upgraded RiskVision server. It is the recommended method to make most UI configurations and using the UICustomization.xml file is a backup for corner cases.
