In EWM, you associate each type of relationship to a versioned artifact (such as implementsRequirement) with a work item property from which a release may be obtained, such as Filed Against or Planned For. All the relationships of the same type will be associated with the same release(s), and hence GCs.

Prior to 7.0.2, an EWM release (aka deliverable) could be associated with a maximum of one GC. That means that in DOORS Next, you would only see an incoming link from the work item to some requirement if you had chosen that [single] GC as your configuration context in DOORS Next.

In 7.0.2, the data representation was changed to store a link to zero, one, or many releases on a GC. So a release may be associated with zero, one, or many GCs. This association is used when determining incoming links from work items to requirements in DOORS Next, or test artifacts in ETM. So if you have two global streams linking to a release R, and that release R is associated with a relationship from the work item in EWM to a requirement in DOORS Next, then you would see that incoming link to that requirement using either of those two global streams as your configuration context.

Best regards,
David.