I hate to be the bearer of bad news, but... yeah, you
probably do. (You might want to consider using zip
codes, as that might allow you to enter fewer
combinations.)
BTW, so that users can manually apply a rule to place the
lead into a sales territory themselves (state was wrong,
e.g) and to minimize code changes when the territory
responsibility changes, I structured my workflow rules
like this:
1) For each territory, create a manual rule with no
conditions that assigns the lead to the current territory
owner.
2) Create a manual rule for each territory that "tests"
if this lead belongs to this territory (This is where all
of your state logic would go. If state = OR, then exec
sub-process for that territory
3) Create a manual rule that execs all of rules in #2
4) Create a Lead Create rule that execs #3.
This way, you will get the lead assignment on initial
save; users can either explicitly override your
assignment, or run the test to place it in the 'correct'
territory; and when a sales person leaves, you only have
to change one line in one workflow rule (from the #1 set
above).
HTH,
Dave
davidlcarr_removebetewenunderscores_@earthlink.net
