Comments
Within outbound we have a master Segment and then multiple sub-segments that help split out contacts into multiple groups with each subsequent group checking to ensure that the members are not in the previous group.
So for a given campaign - this includes grouping contacts by those that should not be contacted, should be emailed (and then if they bounce, would fall into the subsequent postal groups) and should be contacted by UK post, should be contacted via Overseas mail and those that have special processing instructions.
Breaking down into the sub-groups ensures that numbers all reconcile and add backup to the Master list and no-one is lost in the process.
The query logic builder is fairly simplistic, and replicating the logic from one segment query to the next (and making it more complex each time) is not feasible/practical.
I think this is only the first step.
Why don't have a setting where we can enable on user level which languages we would like to use for the Search.
e.g. always use the user language as default language, but there can be users that would prefer another language as default search language.
e.g. If I'm on a austrian environment I might prefer search results for de-DE instead of de-AT.
And I'm totally for the english search results. (This did work in BC22, but doesn't work anymore in the latest BC Version)
e.g. Job Queue Entries can be found easier than the german translation .