I wrote up a detailed article a few weeks ago describing how to create a SharePoint Designer workflow that sends a task reminder email on a daily basis. It’s been published at the new SharePoint Magazine suíomh. More generally, Léiríonn an tAirteagal seo conas a chruthú struchtúr looping i SPD.

The magazine has a wide variety of articles including, i measc nithe eile, very technical stuff, interviews and industry news. I recommend you add it to your RSS feed.

If you have a product or service to sell, I’d also consider advertising on the site. It’s off to a strong start with several thousand pairs of eyes looking at it already. That’s sure to grow.

Ar deireadh, if you’ve been itching to write something and get it out in front of a larger audience, this is a great time and place to scratch it.

</deireadh>

Liostáil le mo bhlag.

Mark Miller thar ag Úsáideoir SharePoint Deireadh has posted my latest article about using SharePoint Designer to create great workflow solutions up on his site. Seiceáil sé amach.

San Airteagal seo,, Labhair mé faoi ar an bpróiseas a dhearadh agus a, níos mionsonraithe, conas a chur ar bun le próiseas tástála iontaofa agus aithrise ag baint úsáide as gnéithe SharePoint (liostaí saincheaptha, teimpléid suíomh). The article targets End Users, ach tá an cur chuige maith d'fhorbróirí ró-.

</deireadh>

Liostáil le mo bhlag.

An tseachtain seo caite, Bhí mé ag obair amach conas a lúb agus meaisín stát chun feidhme ag baint úsáide as Dearthóir SharePoint agus a luaidhtear, mar leataobh, go Ba mhaith liom a scríobh is dócha go bhfuil post blag faoi lománaíocht sreabhadh oibre níos fearr.

Bhuel, Sanjeev Rajput beat me to it. Bíodh Féach.

Shábháil sonraí logáil isteach liosta saincheaptha is cosúil níos fearr chun úsáid a bhaint as an stair sreabhadh oibre rialta:

• Tá sé ach liosta saincheaptha, ionas gur féidir leat é a onnmhairiú go dtí barr feabhais an-éasca.
• Is féidir leat a chruthú tuairimí, dinimiciúil scagadh na sonraí, etc.
• Níl sé faoi réir an auto-purge a fhaigheann tú le stair sreabhadh oibre rialta.

Tá roinnt priacal / downsides:

• D'fhéadfadh go leor sreabhadh oibre ag rith le go leor de chúis logáil sonraí i bhfad ró-a bheith scríofa ar an liosta.
• Maybe you *do* want automatic purging. You don’t get that feature with this approach (gan códú).
• Security is tricky. In order to write to the list, the user must have permission to do so. That means that it’s probably not suitable for any kind of "official" audit since the user could discover the list and edit it. This could be overcome with some custom programming.

</deireadh>

Liostáil le mo bhlag.

This past week I finished off a proof of concept project for a client in Manhattan. While implementing the solution, Rith mé isteach i easnamh eile de MOSS KPIanna (féach anseo le haghaidh eisiúint KPI roimhe sin agus mo workaround).

Cúlra: We used SharePoint Designer workflow to model a fairly complex multi-month long business process. As it chugged along, it would update some state information in a list. KPIs use this data to do their mojo.

We decided to create a new site each time a new one of these business processes kicks off. Aside from the workflow itself, na suímh éagsúla leabharlanna doiciméad óstach, use audience targeting and so forth. Just a bunch of stuff to help with collaboration among the internal employees, fostaithe agus páirtithe an chliaint gnó rannpháirteach taisteal.

Theastaigh uainn freisin chun a thaispeáint roinnt KPI go monatóireacht a dhéanamh ar an iomlán sláinte an bpróiseas gnó ar leith chun cinn ag na sonraí stáit sreabhadh oibre agus féachaint air ag baint úsáide as na KPI.

Mar fhocal scoir, a úsáid le linn míreanna liosta TFB go bhfuil a líon ar an dearcadh ar an liosta sa suíomh (i gcomparáid le tarraingt ó fhoinse eile sonraí, cosúil le excel nó SQL).

An Fhadhb: Mar is féidir leat a shamhlú, ag glacadh leis go raibh muid a dhéanamh ar an smaoineamh bunúsach ar aghaidh isteach i saol táirgeachta, we would want a site template. Provision a new site based off a "business process" teimpléad.

The problem is that you can’t seem to get a functioning KPI that way. When I create a new site based on a template with a KPI List and KPI web part, the new site’s KPI data are broken. The new site’s KPI list points at whatever source you defined when you first saved it as a template.

Mar shampla:

• Create a new site and build it to perfection. This site includes the KPI data.
• Sábháil go mar theimpléad.
• Cruthaigh suíomh nua agus bonn má as an teimpléad.
• Míreanna seo suíomh nua ar liosta PTF’ pointe foinsí leis an teimpléad láithreán, nach bhfuil an suíomh reatha.

Ní dhéanann an próiseas instantiation cheartú an URL.

I tried to solve this by specifying a relative URL when defining the KPI list item. Mar sin féin, Ní raibh mé in ann a fháil ar aon athrú a bheith ag obair.

I always want to pair up these "problem" blog post le roinnt de chineál réiteach, but in this case I don’t have a good one. The best I can figure is that you need to go in to the newly provisioned site and fix everything manually. The UI makes this even harder because changing the URL of the source list causes a refresh, ionas go mbeidh tú i ndáiríre a ath-shainmhíniú ar an rud ar fad ó scratch.

Má tá aithne ag duine ar bith ar bhealach níos fearr chun déileáil leis seo, le do thoil post a comment.

</deireadh>

I’ve recently learned that it’s possible and even fairly easy to create a state machine workflow using SharePoint Designer. Necessity is the mother of invention and all that good stuff and I had a need this week that looked for an invention. Coincidentally, Tháinig mé trasna an bhfóram seo MSDN post chomh maith. My personal experience this week and that "independent confirmation" lends strength to my conviction. I plan to write about this at greater length with a full blown example, ach anseo tá an gist sé:

• Ghiaráil an cur chuige ar an bhfíric gur féidir le sreabhadh oibre a athrú le mír liosta, thereby triggering a new workflow. I’ve normally considered this to be a nuisance and even blogged faoi ag baint úsáide as semaphores a láimhseáil.
• SharePoint Ceadaíonn sreabhadh oibre neamhspleách il a bheith gníomhach i gcoinne ítim liosta ar leith.

A chumrú sé:

• Dear do mheaisín stáit (i.e., an stáit agus an chaoi a aistriú stáit ó cheann go ceann eile).
• Chur i bhfeidhm gach stát mar sreabhadh oibre ar leithligh.
• Cumraigh gach ceann de na sruthanna oibre stáit a fhorghníomhú mar fhreagra ar aon athrú ar an mír liosta.

Leanann gach sreabhadh oibre luaigh an patrún garbh:

• Ar initialization, determine whether it should really run by inspecting state information in the "current item". Abort if not.
• An bhfuil an obair.
• Update the "current item" with new state information. This triggers an update to the current item and fires off all the state workflows.

Chomh maith as an sochar soiléir gur féidir le duine a chruthú sreabhadh oibre meaisín declarative stáit, Is léir go bhfuil an fhaisnéis stát iontach do KPI tógála agus tuairimí suimiúla.

Déanann sé go mbeadh míbhuntáiste suntasach go cothrom — standard workflow history tracking is even more useless than normal 🙂 That’s easily remedied, áfach,. Store all of your audit type information in a custom list. That’s probably a good idea even for vanilla sequential workflow, but that’s for another blog post 🙂

I call this a "mea culpa" toisc go bhfuil mé, ar an drochuair, said more than once on forums and elsewhere that one must use visual studio to create a state machine workflow. That simply isn’t true.

</deireadh>

Liostáil le mo bhlag.

It’s possible to cause an endless loop in a SharePoint Designer workflow. A common implementation pattern like this causes the problem:

• Cruthaigh sreabhadh oibre agus a cheangal le liosta.
• Léirigh gur chóir dó tús a chruthú ar na míreanna nua agus suas chun dáta de na míreanna atá ann cheana féin.
• Céim sa sreabhadh oibre suas chun dáta le réimse i "Ítim Reatha".
• Ós rud é athraigh an mhír reatha, Tosaíonn an sreabhadh oibre as an nua.

Chun cosc ​​a chur leis an lúb endless, a chur i bhfeidhm Semaphore simplí:

• Cuir colún suíomh (nó colún ar an liosta / leabharlann más rud é nach bhfuil tú ag baint úsáide as cineálacha ábhar).
• Folaigh sé as an leathanach in eagar (éasca a dhéanamh más rud é colún suíomh trí a n-airíonna, Ní furasta amhail is dá colún liosta).
• I sreabhadh oibre, seiceáil a fheiceáil má tá luach an colún Semaphore bán.
• Má tá sé folamh, sé síos ar luach neamh-bán agus dul ar aghaidh.
• Más rud é nach bhfuil folamh, scoir láithreach.

Is féidir é seo a réiteach go cothrom nuanced, ag brath ar riachtanais ghnó agus mar sin de, ach atá sé patrún inoibrithe nuair a bhí mé ag teastáil sé.

</deireadh>

Liostáil le mo bhlag.

Mar is eol go leor daoine, an teimpléad Oiliúint Fostaithe ar fáil ag Microsoft anseo Tá a bug gur féidir linn a atáirgeadh leanas na céimeanna seo:

• Cruthaigh rang a bhfuil méid uasta de 10 mac léinn.
• Cláraigh –> Total available seats properly decrements by one. Toradh: 9 suíocháin atá ar fáil.
• Unregister: –> Bug. Total available seats should increment by one. It does not. Toradh: 9 suíocháin atá ar fáil de réir SharePoint, ach i ndáiríre, tá 10 suíocháin atá ar fáil.

Réiteach: Bain úsáid as SharePoint Dearthóir a cheartú ar an sreabhadh oibre.

An Chéad, open up the site. The folder list for me looks like this:

If we have a look at the "Attendee registration" sreabhadh oibre, we see that there is a step labeled "Enforce seating policy". It looks like this:

This step in the workflow updates the item by incrementing the "Filled Seats" metadata column on the course. If we pull that up in more detail, feicimid seo:

Sin an fhaisnéis go léir is gá dúinn a shocrú ar an sreabhadh oibre unregistration.

Má táimid smeach thar an sreabhadh oibre unregistration, there is no similar workflow step. Add it as follows:

1: Expand "Attendee unregistration" agus a oscailt suas ar an XOML (féach ar scáileán lámhaigh chéad má tá tú caillte).

2: Cuir athróg sreabhadh oibre nua, "New Filled Seats" of type "Number".

3: Assign a value to "New Filled Seats" mar a thaispeántar:

4: Decrement na suíocháin Líonta trí 1:

5: Nuashonraigh an mír Cúrsa gaolmhar:

6: Make sure all the steps are in the right sequence. Maidir liom féin, tá sé cosúil leis an:

7: Críochnaigh an sreabhadh oibre a ath-thógáil air.

8: Tástáil.

</deireadh>

Liostáil le mo bhlag.

Ceann de na patrúin ag teacht chun cinn a aimsiú mé i crafting réitigh SharePoint SharePoint ghiaráil Dearthóir sreabhadh oibre agus glacadóir ócáid.

Seo cás gnó a chur i gcomhthéacs:

• Mé doiciméad a uaslódáil chuig lib doc.
• Ciceáil mé amach sreabhadh oibre il-chéim a cruthaíodh ag baint úsáide as SharePoint Dearthóir.
• Ag pointe éigin i rith an phróisis, sreabhadh oibre shannadh tasc le duine éigin (trí shonraí ó úsáideoirí a bhailiú nó tasc a shannadh).
• We want to use a KPI to track how long that task is awaiting completion. The KPI shows green for tasks that are completed or due more than 3 days from now. It shows yellow if the task is due tomorrow or today. It shows red if the task is past due.
• Seo an Kicker: Ba mhaith liom an dáta a thiomáineann an TFB a bheith ar saoire-eolas.

I can’t calculate a holiday-aware due date in SharePoint Designer workflow very easily. I would have to create a custom action or use a 3rd party tool. Mar sin féin, it’s easy enough to calculate such a date in an event receiver. Merge those two together and we get a pattern like this:

• Define a hidden yes/no site column on the document library labeled "DoCalcualteDueDate".
• Sé thúsú go bréagach.
• Ag an am cuí sa sreabhadh oibre (e.g. just before the "collect data" gníomh), luach sin a shannadh do True.
• An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" Is é de ghnáth bréagach.
• Nuair a shannadh sreabhadh oibre DoCalculateDueDate go fíor, Ríomhann an glacadóir ócáid ​​an dáta dlite saoire-eolas.
• Nuair a dhéanann an glacadóir ócáid ​​seo a ríomh, Leagann sé an bhratach DoCalculateDueDate go bréagach.

Sa deireadh, SPD workflow is communicated with an event receiver via the DoCalculateDueDate semaphore and we have holiday-aware due dates that are assigned at the exactly correct moment in the workflow’s life. SharePoint Designer controls when the due date is assigned but the event receiver performs the actual calculation and assignment.

</deireadh>

Liostáil le mo bhlag.

Suas chun dáta: I’ve been researching how to embed a SPD workflow into a site definition. Tá roinnt eolais suimiúil an slabhra fóram MSDN. It’s not conclusive, ach pointí chun cosán tríd an jungle.

I’m giving this post a slightly oddball "Observed Behavior" lead since I’m a little leery of drawing conclusions from it. SPD workflows are … temperamental.

Daoine ag iarraidh go minic / wondering / fretting over moving SPD workflows from one place to another. Sa lá atá inniu, Lean mé ar na céimeanna seo agus rinneadh na tuairimí:

• Chruthaigh mé ag baint úsáide as sreabhadh oibre SharePoint Dearthóir i suíomh gabháil le leabharlann doiciméad.
• An leabharlann doiciméad gaolmhar lonnaithe cheana féin roinnt cáipéisí.
• Shábháil mé an suíomh seo mar theimpléad.
• Nuair a Shábháil mé an suíomh seo mar theimpléad, Shábháil mé an t-ábhar chomh maith.
• Chruthaigh mé suíomh nua sa bhailiúchán suíomh céanna ag baint úsáide as an teimpléad.

Ag an bpointe seo, I tried to run the workflow. It promptly terminated itself with the log message, "Failed on start".

I expected this. I have low expectations when it comes to moving SPD workflows around.

Lean mé:

• Osclaíodh an suíomh i SharePoint Dearthóir.
• Had a peek at the workflow. It seemed fine.
• I clicked "Finish".
• Rith mé an sreabhadh oibre.

An uair seo, d'oibrigh sé fíneáil.

I’ll add that this workflow used the "collect data from user" ghníomhaíocht a bheadh ​​gníomh sách casta faoi na cochall.

I tentatively conclude that the process of "finishing" the workflow caused SPD to properly associate the SPD workflow with the new document library. I also conclude the XOML and other XML artifacts are reasonably "loose". They are not super tightly coupled to the document library.

Cad a chiallaíonn sé seo? Assuming it’s a reliable and reproducible process, there’s at least one rough method we can use to move them around. I don’t know if this would work if we crossed site collection boundaries or even more drastically, feirmeacha ar fad nua (e.g. dev chuig céim a dtáirgí).

Má tá tú ag léamh seo agus claonta, le do thoil post a comment nó ríomhphost chugam your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</deireadh>

Liostáil le mo bhlag.

It’s often useful to store status information in a custom list such as an approval code which should never be directly manipulated by end users. This is a common business scenario. I have been working on a project this year that generates various status and reminder dates via SharePoint Designer workflows that then drive KPIs and generally support time-critical business processes.

Bain úsáid as cineál ábhar an tsuímh / colún a bhaint amach i bhfeidhm.

Cruthaigh cineál ábhar an tsuímh leis an gcolún ar stádas mar a thaispeántar:

Note the "Status (le haghaidh Demo)" réimse ag bun an leathanaigh.

Ar Aghaidh, click on the column name to access the column’s properties. Select "Hidden (Ní bheidh le feiceáil i bhfoirmeacha)" sa Colún alt Socruithe mar a thaispeántar:

This removes the field from the standard edit/update forms. Mar sin féin, Tá sé ar fáil i tuairimí fós, PTF, an tsamhail réad agus in aon áit eile ba mhaith leat é a úsáid, including SPD workflow.

</deireadh>

Liostáil le mo bhlag.