Problems with relationship constraints
Hi I am using RAM version 7.5.1 on the IBM Enterprise Cloud and I am experiencing 2 problems with the relationship constraint on asset types.
I have a Global asset called Service Contract, used in a community setting the choice "Override the configuration from the global asset type" and I have defined 7 relationship constraints.
1 ) The first time when we create an asset, all the allowed relationships are displayed. But after creating the asset, if we want to modify the relationships, only the relationships we previously established are displayed.
I have a Global asset called Logical Data model, used in a community setting the choice "Override the configuration from the global asset type" and I have defined 4 relationship constraints.
2 ) The first time when we create an asset, all the allowed relationships are displayed. But after creating the asset, if we want to modify the relationships, there is a drop-down list with all relationships ? ( on the asset types constraints the choice is set to "Allow only these relationships"
I can't see why there is a difference in behavior between these 2 scenarios ?
The expected behavior is that I get a list with only the allowed relationship in both cases.
can somebody help ?
I have a Global asset called Service Contract, used in a community setting the choice "Override the configuration from the global asset type" and I have defined 7 relationship constraints.
1 ) The first time when we create an asset, all the allowed relationships are displayed. But after creating the asset, if we want to modify the relationships, only the relationships we previously established are displayed.
I have a Global asset called Logical Data model, used in a community setting the choice "Override the configuration from the global asset type" and I have defined 4 relationship constraints.
2 ) The first time when we create an asset, all the allowed relationships are displayed. But after creating the asset, if we want to modify the relationships, there is a drop-down list with all relationships ? ( on the asset types constraints the choice is set to "Allow only these relationships"
I can't see why there is a difference in behavior between these 2 scenarios ?
The expected behavior is that I get a list with only the allowed relationship in both cases.
can somebody help ?
One answer
There seems to be a bug in this area. The problem I see is
1. Create a global attribute type
2. Override the type in the community and create relationship constraints
3. Check the 'Allow only these relationships' checkbox
When the asset is submitted for the first time, only the relationships for which constraints are defined are available. When the asset is modified, all relationships are available. I produced this in both 7.5.1 and 7.5.1.1.
I have opened the following defect.
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/67693
1. Create a global attribute type
2. Override the type in the community and create relationship constraints
3. Check the 'Allow only these relationships' checkbox
When the asset is submitted for the first time, only the relationships for which constraints are defined are available. When the asset is modified, all relationships are available. I produced this in both 7.5.1 and 7.5.1.1.
I have opened the following defect.
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/67693