Conventions are used for object generation to reduce the customizing effort. A significant example is the automatic transport of attributes from master data to transactional data. For example, the test activities attribute (testingsteps) is automatically transported during test case generation from the test definition to the generated test case via a name convention. When a new attribute to be transported to a transactional data object was introduced in earlier ARIS Risk & Compliance Manager versions, not only the XML configuration, but also the corresponding object generator had to be adapted in the Java source code. From version 4.0, you must assign identical names to the attributes at the source object and target object.