http://blogs.technet.com/b/orchestrator/archive/2012/05/02/orchestrator-quick-tip-null-value-conditions.aspxThere are times when you want to validate that the value of a property isn’t blank. For example, you could be checking the output value (published data) of an activity to make sure it’s not blank before proceeding. However, in the list of available comparisonsen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/orchestrator/archive/2012/05/02/orchestrator-quick-tip-null-value-conditions.aspx#3570126Wed, 01 May 2013 08:19:15 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3570126Kenneth Sundby<p>Why not just use &quot;Parameter 1 from Initialize Data equals&quot; and leave the value empty?</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3570126" width="1" height="1">http://blogs.technet.com/b/orchestrator/archive/2012/05/02/orchestrator-quick-tip-null-value-conditions.aspx#3496119Fri, 04 May 2012 15:36:55 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3496119Rob Campbell<p>In some cases \S may be a more desirable match pattern. A field or line that appears empty may actually contain whitespace that $^ would fail to match on.</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3496119" width="1" height="1">