Hi team,

In OBM, users have the ability to traverse multiple entities and filter within each entity.

However in RTJ, although traversing multiple entities is possible, filtering (or defining attributes) is only limited to the top most entity.

USE CASE:

In our scenario, we have 3 entities -> Organisation, Membership, and Contacts (native entity). 

• Organisation to Membership: 1 to many (1 organisation contains multiple subscribing members)
• Membership to Contact: many to 1 (1 person could potentially own multiple organisation and hence separate membership agreement)

In OBM, I can define to say find Contacts where they have an Active Membership that is sitting under an Active Organisation.

In RTM though, I can only find Contact where they have an Active Organisation, AND ALSO Contact where they have an Active Membership.

While on the surface it looks the same, technically this is not right.

Consider the scenario where we have a Contact that has 2 membership:

• One where their Membership is Active sitting in an Inactive Organisation.
• One where their Membership is Inactive sitting in an Active Organisation.

In OBM, this person should not be picked up, but in RTJ, it would have been picked up.

Users should be allowed to filter while traversing like what OBM can offer.