- CWLAF0001E: A managed role was already defined for relationship "{0}". One managed role is the maximum allowed for identity relationships.
- Explanation: Multiple managed roles are not valid for identity relationships.
- User Action: Deactivate the unnecessary managed roles.
- CWLAF0002E: No managed role was defined for relationship "{0}". One managed role is mandatory for identity and non-static relationships.
- Explanation: For identity and non-static relationships, a managed role is required.
- User Action: Define one managed role.
- CWLAF0003W: Managed roles are not used in non-identity relationship "{0}".
- Explanation: For a non-identity relationship, a managed role is not necessary.
- User Action: Review the definitions and deactivate the managed role.
- CWLAF0004E: The key attribute should be defined in a non-managed role for role "{0}".
- Explanation: For a non-managed role, the key attribute should be defined.
- User Action: Define the valid key attribute.
- CWLAF0005E: Only one key attribute is allowed in a managed role for role "{0}".
- Explanation: For a managed role, the number of key attributes should be 1.
- User Action: Define one key attribute.
- CWLAF0006E: The forward slash character, '/', is not allowed at the beginning of the path.
- Explanation: '/' is not a valid character to start the path.
- User Action: Never use '/' to start the key attribute path.
- CWLAF0007E: The forward slash character, '/', is not allowed at the end of the path.
- Explanation: '/' is not a valid character to end the path.
- User Action: Never use '/' at the end of the key attribute path.
- CWLAF0008E: Only one forward slash character, '/', is allowed in a path element.
- Explanation: '//' is not allowed in a path.
- User Action: Never use multiple forward slashes, '//', in the key attribute path.
- CWLAF0009E: A relationship "{0}" already exists in the scope.
- Explanation: The relationship name is already used in the scope.
- User Action: Change the relationship name.
- CWLAF0010E: A role with the duplicate name already exists in relationship "{0}".
- Explanation: The role name is already used in the scope.
- User Action: Change the role name.
- CWLAF0011E: A business object "{0}" does not exist in the scope.
- Explanation: The business object is not defined in the scope.
- User Action: Change the reference business object or add the corresponding business object definition.
- CWLAF0012E: A business object attribute "{0}" does not exist in the business object definition.
- Explanation: The attribute is not defined in the business object.
- User Action: Add the attribute in the business object or refer to another attribute.
- CWLAF0013E: A relationship "{0}" is not defined in the scope.
- Explanation: The relationship is not defined in the scope.
- User Action: Either change the reference to a valid relationship, or add the corresponding relationship definition.
- CWLAF0014E: A role "{0}" is not defined in the scope.
- Explanation: The role is not defined in the scope.
- User Action: Either change the reference to a valid role, or add the corresponding role definition.
- CWLAF0015E: A property "{0}" is not defined in the relationship or role "{1}".
- Explanation: The property is not defined in the relationship or role.
- User Action: Either change the reference to a valid property or add the corresponding property definition.
- CWLAF0016E: A key attribute "{0}" is not defined in the role "{1}".
- Explanation: The key attribute is not defined in the role.
- User Action: Either change the reference to a valid key attribute or add the corresponding key attribute definition.
- CWLAF0017E: The key attribute value is not specified for the instance data for role "{0}".
- Explanation: The key attribute value is not specified.
- User Action: Specify an attribute value.
- CWLAF0018E: The .ri file refers to the wrong XSD file.
- Explanation: The .ri file is not consistent with the corresponding XSD file.
- User Action: Change the .ri file.
- CWLAF0019E: The data for property "{0}" is already defined in the relationship "{1}".
- Explanation: The data for the same property appears more than once in the instance definition.
- User Action: Define the property data only once.
- CWLAF0020E: The data for property "{0}" is already defined in the role "{1}".
- Explanation: The data for the same property appears more than once in the instance definition.
- User Action: Define the property data only once.
- CWLAF0021E: The data for the key attribute "{0}" is already defined in the role "{1}".
- Explanation: The data for the same key attribute appears more than once in the instance definition.
- User Action: Define the key attribute data only once.
- CWLAF0022E: The specified data type "{0}" is an invalid XML type.
- Explanation: The data type is not valid.
- User Action: Use a valid XML type.
- CWLAF0023E: A managed role is not allowed in the static relationship "{0}".
- Explanation: For a static relationship, a managed role is not used.
- User Action: Deactivate the managed role.
- CWLAF0024E: The value of the key attribute "{0}" is not specified.
- Explanation: The value is not specified for the key attribute.
- User Action: Specify a valid value.
- CWLAF0025E: The value of the key attribute "{0}" is empty.
- Explanation: The value of the key attribute is empty.
- User Action: Specify a value.
- CWLAF0026E: The role instance data is not specified for the instance id "{0}".
- Explanation: The role instance data is not specified.
- User Action: Specify a role instance data.
- CWLAF0027E: The index is not specified for the multiple cardinality attribute "{0}" in the path "{1}".
- Explanation: Skipped levels of child Business Objects are not allowed if this child Business Object is of multiple cardinality and no index is specified for it.
- User Action: Specify an index for the skipped level of a child Business Object of multiple cardinality.
- CWLAF0028E: The attribute with the path "{0}" is not allowed as a key attribute for the role "{1}", because there exists another key attribute from the different child Business Object that belongs to the same parent Business Object.
- Explanation: Key attributes from the different child Business Objects that belong to the same parent Business Objects are not allowed in a role.
- User Action: Remove the invalid key attribute.
- CWLAF0029E: The role "{0}" contains an invalid key attribute with path "{1}". A key attribute can only be a simple type property of a BO, and it is not allowed to have a complex type property as the key attribute.
- Explanation: A key attribute can only be a simple type property of a Business Object, and it is not allowed to have a complex type property as the key attribute.
- User Action: Remove the invalid key attribute.
- CWLAF0030W: The index can not be specified for the single cardinality attribute "{0}" in the path "{1}".
- Explanation: It is not valid to specify an index for a single cardinality attribute.
- User Action: Remove the index from the key attribute.
- CWLAF0031E: An index should be specified for the array attribute "{0}" in the path "{1}".
- Explanation: Array property of a Business Object should have an index specified.
- User Action: Specify an index for the key attribute.
- CWLAF0032E: At least one key attribute from the parent Business Object should be defined for the role "{0}".
- Explanation: Specifying at least one key attribute from the parent Business Object is required for the role.
- User Action: Define at least one key attribute from the parent Business Object.