Hey, everybody, Larry’s opportunity pipeline this month is again bigger than everyone else’s. Larry, what’s your secret?
Larry, being somewhat softened by reasonable quantities of flavored C2H5OH, was more than happy to share his fortunes:
It’s all about power of automatic workflows, my friends. See how I automatically increase opportunity value the moment it’s created?
But if it’s automatic how come our records stay the same?!
No idea, but it works for me!
The secret sauce, of course, is frequently overlooked scope of the automatic workflows.
If user creates a workflow and sets the scope to, ahem, User, then this workflow will only kick in for the records owned by this user. This setting, frequent source of workflow creators’ frustration, is a powerful tool to create private functionality scoped to individual, business unit, business unit and children, as defined by the current workflow owner and her business unit.
One useful application of that feature is ability to craft your workflow in production right under the nose of unsuspecting administrators. Set the scope to the user, work on your private records, make sure the workflow works as expected then change the scope to, say, organization.