SharepointFrancois http://sharepointfrancois.posterous.com Ex-Domino consultant went to the Microsoft Sharepoint some years ago, and rumble his thoughts and findings posterous.com Thu, 09 Aug 2012 02:23:00 -0700 Clever idea : Approve or reject tasks via email WITHOUT Nintex http://sharepointfrancois.posterous.com/clever-idea-approve-or-reject-tasks-via-email http://sharepointfrancois.posterous.com/clever-idea-approve-or-reject-tasks-via-email
Check out this website I found at gallery.technet.microsoft.com

I have to say when it comes to responding a workflow task while being mobile I think of advising my clients to buy Nintex Workflow for their Sharepoint farm as the design and maintenance of those workflows is much, much cost effective in the long term. But this post got me thinking, specially when you have an IT environment locked down where you cannot add third party tools.
I have not implemented it myself yet, but will do in a few weeks.

Permalink | Leave a comment  »

]]>
http://files.posterous.com/user_profile_pics/1375377/me_avatar.jpg http://posterous.com/users/hcksWlFw5buwq Francois Souyri nicofars Francois Souyri
Wed, 08 Aug 2012 04:02:00 -0700 Avoid '&' (Ampersand) sign in Nintex workflow variable values http://sharepointfrancois.posterous.com/avoid-ampersand-sign-in-nintex-workflow-varia http://sharepointfrancois.posterous.com/avoid-ampersand-sign-in-nintex-workflow-varia

Issue:

 I have a main workflow that calls 16 different sub-workflow to run and wait for their completion before continuing and to my surprise only 1 of those didn't send me an email as I expected it to be, but did not fail nor stopped.

 

Troubleshooting:

 The sub-workflows are all running and complete, then the main workflow continues its journey to completion.

Nintex16

By adding a Log in History to extract all the variables that I pass to the sub-workflows I then realised that the only difference between all sub-workflow and the one that flies through without sending an email contains a '&' character in one of the variable. That variable is just used to print the value in the body of the message, not even the subject or the recipient email but still it did fail the workflow action.

 

Fix:

by adding a "Regular Expression" Nintex action we can easily replace any ampersand in variable before passing it to the sub-worklow. If you place it into the sub-worlfow UDA then it's only 1 change for all 16+ sub-workflows.

 

Note to self: filter out & character (ever)

Permalink | Leave a comment  »

]]>
http://files.posterous.com/user_profile_pics/1375377/me_avatar.jpg http://posterous.com/users/hcksWlFw5buwq Francois Souyri nicofars Francois Souyri