Last week, Mark Miller posted my latest SharePoint Designer workflow article for end users on his site (http://www.endusersharepoint.com/?p=1226).

It starts like this:

We technical types use a lot of jargon and acronyms in our daily routine such as “OOP” (object oriented programming), “CT” (Content Types), “SPD” (SharePoint Designer), “RTFM” (please read the manual), etc.  This article concerns itself with a particular bugaboo called “hard coding:” What it is, why it’s bad and how to avoid it in SharePoint designer workflow solutions.

I describe how we can use custom lists to store workflow control and configuration data.  Using this approach, we can avoid hard coding values such as approvers’ email addresses, approval dollar limits, etc. 

Check it out.

</end>

Subscribe to my blog.

Follow me on Twitter at http://www.twitter.com/pagalvin