What can be customized?

The configuration of ARIS Risk & Compliance Manager is defined in XML files based on commented XML schema files (.xsd). These XML files describe:

The XML configuration refers to:

You can customize the application by adapting the elements in the XML configuration.

For example, you can add an existing attribute type to an existing object type using a new name. Or you can include new elements, such as new messages or Java classes implementing new behavior that you cannot otherwise configure using XML. This does not require an individual build process. Changes to the configuration are applied during server runtime as long as the system is running in development system mode (ACC parameter arcm.config.isDevelopmentSystem = true). A server restart is required for productive systems. The section Basic use cases describes all steps for adaptations based on the XML configuration.

You can also customize the behavior by integrating individual Java implementations of special interfaces through the XML configuration. These Java classes can be individually developed based on a defined interface and are then included like the default classes without any particular build process being required for ARIS Risk & Compliance Manager.