Prevent adding member to engagement stream if already a member of another stream.

[Dan_Stevens_]

We have three streams of content in an enagement program.  Before we add new members to a stream of content, we first want to make sure they're not already in an existing stream - meaning, they're already a member of a specific engagement program.  If I use the "Member of Engagement Program = FALSE" choice (see flow step below), will this prevent them from being added as intended?  Or does this choice refer to ANY enagagement programs (and we have several throughout our instance).

[Dan_Stevens_]

Thanks guys. Unfortunately, including that as part of the smart list will prevent the program status to change for those members who convert and are already members of the engagement program. So that's not an option.

[Josh_Hill13]

Dan,

Try creating a smart list that includes everyone who is a member of Engagement.

Then change your Choice to Member of Smart List NOT IN 

that should work more efficiently for you.

Otherwise,yes, Member of Engagement=False should be working, but you can only select one at a time, so this step choice method isn't really a good idea. What you are trying to do this essentially a traffic cop.

[Anonymous]

This will refer to any engagement program. Can you push the logic to the Smart List instead of the flow step? There is a constraint on Program Name there you can use.