As soon as you customize object properties, you must overwrite the schema tag from the file objectTypes.xml in customizing. This is the only way to ensure that data exports and imports from the customized ARIS Risk & Compliance Manager version can be properly assigned to the relevant version. The customizing of the version also serves as a fixed starting point for future migrations. If you do not overwrite the schema tag, but still make changes to the schema, it will not be possible to start the ARIS Risk & Compliance Manager Server.
Procedure
Enter the name of the customer project without blanks in the customizing attribute in the overwritten schema tag. This attribute has the value standard if the schema has not been customized.
Example
Entry for a customer project called United Motor Group on the basis of ARIS Risk & Compliance Manager version 10 Service Release 10:
<schema version="10.0.10" customizing="UnitedMotorGroup" />
If different customer versions based on a single ARIS Risk & Compliance Manager version are to be supplied, you can indicate this by stating a version number in the project name.
Example
Entry for a customer project called United Motor Group version 1 on the basis of ARIS Risk & Compliance Manager version 10 Service Release 10:
<schema version="10.0.10.0" customizing="UnitedMotorGroup_v1" />
If changes in the ARIS Risk & Compliance Manager schema are due to a change in the data import from ARIS Architect, you must also adapt the target schema in the relevant mapping file Aris2arcm-mapping.xml.
Procedure
schema_version="10.0.12.0_standard"
Example
schema_version="10.0.12.0_UnitedMotorGroup"