Best Practice Suggestions: Different Groups in 1 Instance not needing shared Fusion scenarios

[jjjonhunt]

SOS -- Hi all. 

Our team is in the process of adding in our Canada group that does similar work. However, their workflow is slightly different and does not need the same degree of automation (mostly Fusion scenarios) to drive their workflow. I am running into errors in SB01 as we do some intake/request queue test for this new group that are tripping a Request Conversion scenario. Would a solve simply be to add a filter at the front end of that scenario to effectively avoid/skip requests from that queue OR is there a better way to set up our Canada team (current just a new Portfolio) that would allow me to not have to edit 10+ fusion scenarios across SB01 and PROD?

APPRECIATE THE HELP!!!

[KellieGardner · Accepted solution]

A couple of ideas:

1) If the queue is set in a different project, you can add a filter for projectID not equal to x

2) If the queue is set in the same project as all the others, then you could filter on queue topic ID or queue topic group

3) If you set this group up as their own "group" in Workfront you can filter out their data by saying the project group ID is not equal to x 

[RandyRoberts]

I concur with Kellie, you're going to have to edit each automation to filter out where you don't want the automation to affect.