Customizing only applies to the specific version number of ARIS Risk & Compliance Manager for which it was implemented. Therefore, customers cannot update to a more recent service or main release of ARIS Risk & Compliance Manager without also updating the customizing. The following steps must be performed each time you update to a more recent version:
Update the version number at customizing:
To enable the new server to use the customizing, you must update the <version> element. Otherwise, the server cannot use the customizing based on an older ARIS Risk & Compliance Manager version. For detailed information, refer to Adapt the XML configuration.
Update outdated customized elements:
Customizing is usually based on overwriting existing elements to meet customer requirements and removing redundant standard functions. The overwritten elements must be checked and, if necessary, migrated or updated with the latest standard fixes and improvements. To obtain a list of all customized items that must be reviewed, use the ANT task Customizing migration: find outdated elements. For detailed information on how to run this task, refer to the CTK documentation chapter Usage of the ANT Toolkit.
Add database migration steps for custom-attributes:
If the customizing attribute at the <version> element was modified for customizing, the database schema is no longer a standard database schema. (For detailed information, refer to Overwrite the schema version.). Therefore, the database migration must be enhanced to process the custom schema changes. For detailed information on how to implement migration steps, refer to CTK documentation chapter Implementing custom database migration steps.
Due to these time-consuming steps to update a customized ARIS Risk & Compliance Manager installation, the advantages and disadvantages of customizing must be reviewed with the customer.