Vroeër hierdie maand, Ek put together an article originally planned for Mark Miller’s www.endusersharepont.com. Egter, I instead used like Dustin Hoffman used a cross at the end of the The Graduate to fend off my (ontsagwekkende! vriendelike!) editor at TechTarget.

This is another SharePoint Designer workflow article in the same vein as my more recent effort here: http://www.endusersharepoint.com/?p=1226 ("Use Control Lists to Create Flexible Workflow Solutions").

Dit begin soos volg:

HAVE YOU EVER wished you could temporarily disable a SharePoint Designer workflow? You may want to do this in order to mass-approve a large number of documents without setting off dozens — or possibly hundreds — of unnecessary workflows.

One way to accomplish this is to access the workflow using Share-Point Designer and disable it. To do that, you’ll need to open up SharePoint Designer, access the workflow, change its properties and re-save it. The problem with that method is that it’s a little messy and likely to ring lots of alarm bells at most companies.

In die algemeen, fiddling about with SharePoint Designer workflows is not a good practice in a production environment, nor is it part of a well controlled process.

The article then walks you through a solution to this problem that uses a custom list to turn the WF on or off as needs dictate. Lees die hele ding hier (http://wp.bitpipe.com/resource/org_1127860336_240/SharePoint_vol5_v6 1_16.pdf).

This article was inspired by a question asked on the forums here: http://www.endusersharepoint.com/STP/. Although I spend far more time on the MSDN forums, I strongly recommend that you have a peek at the EUSP forum as well, particularly for end user oriented questions. It’s yet another source of good information and advice.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Verlede week, Mark Miller gepos my jongste SharePoint Designer workflow artikel vir die einde gebruikers op sy webwerf (http://www.endusersharepoint.com/?p=1226).

Dit begin soos volg:

Ons tegniese tipes gebruik 'n baie jargon en akronieme in ons daaglikse roetine, soos "OOP" (objekgeoriënteerde programmering), "CT" (Inhoud tipes), "SPD" (SharePoint Designer), "RTFM" (Lees die handleiding), ens.. This article concerns itself with a particular bugaboo called “hard coding:"Wat is dit, Hoekom is dit sleg en hoe om dit te vermy in SharePoint ontwerper workflow oplossings.

I describe how we can use custom lists to store workflow control and configuration data. Using this approach, Ons kan voorkom hard kodering waardes soos keurders’ e-pos adresse, goedkeuring dollar grense, ens..

Check dit uit.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

I’m working at a client site and needed to install windows workflow foundation so that I could so some SharePoint Designer work. (Ek het nie geweet tot vandag toe dat SPD installeer fyn, maar regtig nodig het ten minste. NET 2.0 en om Windows Workflow Foundation regtig bruikbare; Ek het altyd aanvaar is geïnstalleer saam met SPD, maar ek was verkeerd).

The client has a proxy server. No problem, I have credentials to get outside to the public Internets. I go to the usual place to download WWF (SPD hulpvaardig voorsien my met 'n skakel). That download is really a bootstrap of sorts. It runs and figures out what else it needs to download. That second download process failed. It either does not try at all, or is somehow prevented from asking for proxy server credentials. It was a pretty hard crash, gee my die boodskap:

Microsoft NET Framework. 3.0 has encountered a problem during setup. Setup did not complete successfully.

Ek het probeer om te herlaai en spandeer 10 seconds trying to figure out if I could get it to ask me for proxy server credentials. I gave up and went here instead: .NET Framework 3.5 Service Pack 1 (Volle pakket).

Ek afgelaai die pakket, geïnstalleer en hierdie keer, die probleme.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin