Dave,
this has been a very helpful thread. I think I am understanding the concepts better. I do believe that I am creating the relationship between two existing objects. I think what has thrown me off is that this new relationship instance also has some attributes. Maybe this new object was created incorrectly.
So, using your terminology;
NOTE: We refer to the stock ROLE object as SUBAREA at my company. This gets a little sticky sometimes when I try to explain things.
I am creating a relationship between the existing things IMPACTS REQUEST and the SUBAREA (role) with the relationship IMPACT_SUBAREA. This new instance has two new attributes (Effort and Comments).
This new relationship (IMPACT_SUBAREA) is a sub object if the IMPACTS REQUEST object. I have tried to create the relationship to the SUBAREA (role) through an attribute which is a lookup to the SUBAREA.
When I click the Add button the portlet is replaced by the new "Create Impacts Subarea" portlet. This is not the "pop-up" that I see on my earlier example of the stock add-to-team example.
I have a look-up field (binoculars) which allows me to select a single instance of the SUBAREA. There is only the Save and the Save and Return buttons (Return too). This only adds one instance of the relationship.
We tried a multi-select lookup, but it want's to concatenate all of the chosen values into a single instance of the IMPACT_SUBAREA.
I have a feeling we are getting close, and this might be one of those learning moments when we figure out how this can be accomplished.
Thanks,
Terry