Hierdie dae, Ek altyd speel met my blog lees inhaal en ek het net oor hierdie post: http://sharepointsolutions.blogspot.com/2009/02/give-blood-to-your-workflow.html
Dit is as vaste en gedetailleerde 'n SharePoint Designer workflow handleiding (plus meer!) that you’ll see anywhere on the interwebs. I’d check it out, even if you’re a scarred SPD veteran.
Dit is 'n groot SharePoint handleiding vir beide Path en workflow.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
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>
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>
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>
Volg my op Twitter http://www.twitter.com/pagalvin
In wat blyk om sy intreerede blog gepos, chiqnlips gedelf in die waansin wat is 'n berekende kolom en beskryf 'n oplossing vir 'n gemeenskaplike SharePoint Designer workflow e-pos aktiwiteit probleem: Hoe om 'n persoon se regte naam te vertoon in 'n e-pos in plaas van "domein gebruikersnaam."
Ek het dit nie getoets myself, but it looks promising. Check dit uit.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Mark Miller oor te www.endusersharepoint.com gepos my jongste artikel oor SharePoint Designer workflow hier (http://www.endusersharepoint.com/?p=1037).
I describe the basic approach for moving a workflow you create in one list to another list. The other list can be in the same site, dieselfde plek versameling of 'n heeltemal ander plaas (bijv. van ontwikkeling tot produksie).
This is a complicated subject so I only covered a very basic scenario. Volgende week, I’ll write up a more useful real world example.
Check dit uit en deel enige kommentaar daar.
<einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Mark Miller het my laaste End User georiënteerde SharePoint Designer Workflow artikel geplaas op sy webwerf hier: http://www.endusersharepoint.com/?p=1008
Ek probeer om 'n reguit-vorentoe antwoord op die vraag te voorsien, "Hoekom kan ek nie maklik hawe 'n SharePoint ontwerper workflow van ontwikkeling om te toets?" In the process, Ek gee ook 'n insig in wat SPD is eintlik agter die skerms toe ons dit gebruik om 'n workflow te skep.
Volgende week, Ek beskryf 'n eindgebruiker vriendelike manier na die hawe SPD workflow van een bediener na 'n ander, of ten minste as eindgebruiker vriendelik 'n oplossing as moontlik is gegewe die toestand van die instrument stel.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Hier is 'n ander gemeenskaplike SharePoint Designer workflow vraag:
"Kan ek toegang tot (lees / skryf) SharePoint 'n lys via van werkstromen wat woon nie op die dieselfde plek as die lys self?"
Die eenvoudige antwoord is: Nie.
Soos in so baie maniere, egter, ons het om te kwalifiseer (wat is 'n goeie ding in hierdie geval). The platform lets us create extensions to the produce in many ways, insluitend 'n persoonlike aksie (sien my klein CodePlex projek hier vir 'n voorbeeld). A custom action lets us do basically anything we want from SharePoint designer workflow. I’m a big fan of this, in werklikheid, want dit gee ons die beste van beide wêrelde — 'n verklarende eindgebruiker-vriendelike ontwerper met die volle diepte van die. NET raamwerk op ons vingerpunte.
Ongelukkig, as jy met SPD, daar is 'n goeie kans dat jy wat jy doen, want jy kan nie visual studio gebruik (as gevolg van die feit dat die Visual Studio vereis 'n diep ontwikkelaar agtergrond). I don’t have any good answer to that problem except that you should prevail upon one of your technical co-workers to create the kind of custom action you need. Alternatively, werk met die bestuur om te huur of kontrak wat soort van die hulpbron.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Ongelukkig, it is not to be. We cannot send an email with attachments from a SharePoint Designer workflow using out of the box features. This wish comes up with increasing regularity on the MSDN forums.
Egter, die SharePoint platform, soos met so baie dinge, does offer us a path forward. Ons kan skep persoonlike aksies which we then incorporate into our workflows. Once installed, 'n persoonlike aksie lyk en voel soos enige ander aksie (bijv. Data in te samel, Meld 'n Boodskap, ens.).
Die skep van 'n persoonlike aksie is 'n groot berg te klim, egter, for End Users. This codeplex project provides this functionality: http://www.codeplex.com/SPDActivities. Pulling that down and installing it is also beyond the skills of typical End Users. Egter, dit is baie maklik vir 'n SharePoint administrateur om dit te doen, So as jy jouself dat daar 'n werk te ontwikkel met die vermoë, werk met jou SharePoint administrateur om dit te doen.
</einde>
Volg my op Twitter http://www.twitter.com/pagalvin
Ons het 'n stel van SharePoint ontwerper werkstromen dat "kommunikeer" with an event receiver on the list via changes to site column values. Byvoorbeeld, indien 'n webwerf kolom "SetDuedate" waar gestel is deur die workflow, die geval ontvanger ontdek dat verandering, word bereken dat 'n sperdatum en ken daardie datum na 'n ander werf kolom, "Due Date." We split things up like this because the event receiver can calculate a due date using complex business rules (naweke en maatskappy vakansies in ag te neem) terwyl die SPD kan regtig nie.
In een spesifieke geval, we ran into a problem with this trick. Debugging all this is pretty difficult, maar ons het tot die definitiewe gevolgtrekking dat in een geval (ten minste), the event receiver was not running all the time. In one step of the workflow, we would change the value of a site column and the event receiver didn’t appear to run. Egter, dit is voortdurend in 'n verskillende stap van die workflow.
Na die lees van, Ek het opgemerk dat die gelukkige workflow stap wat gebruik word om die "Update lysitem" while the other step used "Set Field in Current Item." Update List Item was updating the "current item." I’m not sure why we picked one over the other since they would seem to be doing the same thing.
So … the Update List Item action did cause the event to fire. Aan die ander kant, die Veld in die huidige punt aksie het nie.
Ek gebruik Update Lys item in beide plekke en violet! It worked. [[ Totaal eenkant, Ek speel die viool op 'n daaglikse basis vir byna 15 jaar ]]
Van hierdie, Ek het tentatief glo dat die "Veld" optrede nie veroorsaak geval ontvangers aan die brand, at least some of the time.
This issue bedeviled us for weeks.
Dit is een van daardie "waargenome gedrag" posts. I observed this happen once in a specific environment and I’m making some guesses as to why things happened as they did. If you have any insight into this one, asseblief aandeel in die kommentaar.
</einde>
