CWLAF0001E: A Managed Role was already defined for relationship "{0}". One Managed Role is the maximum allowed for Identity Relationships
Explanation: For Identity Relationship, multiple managed roles are not valid.
User Action: Deactivate unnecessary managed roles

 

CWLAF0002E: No Managed Role defined for relationship "{0}", one Managed Role is mandatory for Identity & Non-Static Relationships.
Explanation: For Identity & Non-Static relationship, managed role is required
User Action: Define one managed role

 

CWLAF0003W: Managed roles are not used in non-identity relationship "{0}". It''s advised that you review your definitions.
Explanation: For non-identity relationship, managed role is not necessary
User Action: Deactivate the managed role

 

CWLAF0004E: The key attribute should be defined in a non-managed role for role "{0}".
Explanation: For non-managed role, key attribute should be defined
User Action: Define valid key attribute

 

CWLAF0005E: One and only one Key Attribute is allowed in a Managed Role for role "{0}" .
Explanation: For managed role, the number of key attributes should be 1.
User Action: Define exactly 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 '/' to end 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 '//' in key attribute path

 

CWLAF0009E: relationship with the name "{0}" already exists in the scope, which should be unique.
Explanation: The relationship name is already used in the scope
User Action: Change the relationship name

 

CWLAF0010E: role with the same name already exist in relationship "{0}", which should be unique.
Explanation: The role name is already used in the scope
User Action: Change the role name

 

CWLAF0011E: the referred BO "{0}" doesn''t exist in the scope
Explanation: The BO is not defined in the scope
User Action: Change the reference BO or add the corresponding BO definition

 

CWLAF0012E: the referred BO attribute "{0}" doesn''t exist in BO definition
Explanation: The attribute is not defined in the BO
User Action: Add the attribute in the BO or refer to another attribute

 

CWLAF0013E: the relationship referred "{0}" is not defined in the scope
Explanation: The relationship is not defined in the scope
User Action: Change the reference to valid relationship or add the corresponding relationship definition

 

CWLAF0014E: The role referred : "{0}" is not defined in the scope
Explanation: The role is not defined in the scope
User Action: Change the reference to valid role or add the corresponding role definition

 

CWLAF0015E: The property referred : "{0}" is not defined in the relationship or role "{1}"
Explanation: The property is not defined in the relationship or role
User Action: Change the reference to valid property or add the correponding property definition

 

CWLAF0016E: The key attribute referred : "{0}" is not defined in the role "{1}"
Explanation: The key attribute is not defined in role
User Action: Change the reference to valid key attribute or add the corresponding key attribute definition

 

CWLAF0017E: The key attribute value isn''t specified for the instance data for role : "{0}"
Explanation: The key attribute value is not specified
User Action: Specify the attribute value

 

CWLAF0018E: the .ri file refer to 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 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 once

 

CWLAF0021E: the data for 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 once

 

CWLAF0022E: the specified datatype : "{0}" is an invalid XML type
Explanation: The datatype should be valid
User Action: Use valid XML type

 

CWLAF0023E: Managed-role is not allowed in the static relationship: "{0}"
Explanation: For static relationship, managed role is unnecessary
User Action: Deactivate the managed role

 

CWLAF0024E: The value of the KeyAttribute must be existing, the name of this KeyAttribute is "{0}".
Explanation: The value is not specified for KeyAttribute
User Action: Specify the valid value

 

CWLAF0025E: The value of the KeyAttribute is empty, the name of this KeyAttribute is "{0}".
Explanation: The value of the KeyAttribute is empty
User Action: Specify the valid value