Mea Culpa — શેરપોઈન્ટ ડિઝાઈનર * * રાજ્ય મશીન વર્કફ્લો બનાવી શકો છો

4 જવાબો

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, I came across this MSDN forum post as well. 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, but here’s the gist of it:

  • The approach leverages the fact that a workflow can change a list item, thereby triggering a new workflow. I’ve normally considered this to be a nuisance and even blogged about using semaphores તે નિયંત્રિત કરવા માટે.
  • શેરપોઈન્ટ બહુવિધ સ્વતંત્ર વર્કફ્લો ચોક્કસ સૂચિ આઇટમ સામે સક્રિય કરવા માટે પરવાનગી આપે છે.

તે રૂપરેખાંકિત કરવા માટે:

  • તમારી રાજ્ય મશીન ડિઝાઇન (એટલે કે, રાજ્યો અને એક ના આગામી કેવી રીતે રાજ્યો સંક્રમણ).
  • અલગ વર્કફ્લો તરીકે દરેક રાજ્ય અમલ.
  • આ યાદી આઇટમ કોઈપણ ફેરફારના પ્રતિભાવમાં ચલાવવા માટે આ સ્થિતિમાં વર્કફ્લો દરેક ગોઠવો.

દરેક રાજ્ય વર્કફ્લો આ રફ પેટર્ન અનુસરે છે:

  • આરંભ કરવા પર, determine whether it should really run by inspecting state information in the "current item". Abort if not.
  • કામ.
  • Update the "current item" with new state information. This triggers an update to the current item and fires off all the state workflows.

કોરે એક ઘોષણાત્મક રાજ્ય મશીન વર્કફ્લો બનાવી શકો છો કે જે સ્પષ્ટ લાભ માંથી, બધા કે રાજ્ય માહિતી મકાન KPIs અને રસપ્રદ વિચારો માટે જબરદસ્ત છે.

તે એકદમ નોંધપાત્ર ખામી હોય છે — standard workflow history tracking is even more useless than normal 🙂 That’s easily remedied, તેમ છતાં. 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" હું કારણ કે, કમનસીબે, 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.

</અંત>

મારા બ્લોગ પર સબ્સ્ક્રાઇબ કરો.

Technorati ટૅગ્સ:

4 પર "વિચારોMea Culpa — શેરપોઈન્ટ ડિઝાઈનર * * રાજ્ય મશીન વર્કફ્લો બનાવી શકો છો”

  3. પીડી Galvin
    That’s a really interesting approach puts an exclamation point on the larger point that SPD can create state machine workflows.
    I don’t know if there are substantial differences performance-wise between what you outline and what I outline. In my case this week, performance isn’t an issue because this particular workflow is a long-running affair (16 or more weeks from start to finish) and there are never more than a few dozen active at any time. If there were a few dozen starting up and running every hour … that would be a different story. I think that performance and workflow in general is a very hazy subject.
    I don’t know if you run your own blog or not. If you do, you ought to consider writing about your approach in more detail. If not, I’d be more than happy to call you a "guest blogger" and upload your post to my blog.
    Thanks for the comment. It’s one of the best I’ve been able to elicit on my blog!
    –પીડી જી
    જવાબ ↓
  4. Mike Atkins
    I implemented the state machine using a separate list to hold the state during the state transitions. The main workflow created an item here and set the initial state. I used a single, separate, workflow to handle all of the states, using an "IF-THEN-ELSEIF" structure (in "Step 1") on the possible states.
    For each state, all I needed to do was obtain a response from a user.
    My example was a multiple-level sequential approval, where each step (represented by a state) could have various possible successors. This meant that each user had (potentially) different options made available in a choice menu. My "Step Two" was also an "IF-THEN-ELSE" structure that considered all of the possible responses (from all stages), and then decided on what the next state should be. "Step 3" then set that state, and the workflow ended.
    This method has the (obvious) advantage of happening within a single (secondary) વર્કફ્લો. તેમ છતાં, the scope of what could be accomplished in this workflow is more limited that one would have with workflows for each state. હું આશ્ચર્ય પામી હતી, તેમ છતાં, what sort of performance hit takes place if all of the individual state workflows start up (albeit ending immediately thereafter).
    પણ, I use a secondary list (with its own workflow) to represent the transition between states as this process might be only part of a larger workflow. When the main workflow starts the state machine process, it goes into a wait state, and proceeds when the "looping" has termintaed. I was also contemplating the possibility that my main workflow may well want to change data in the original List Item, and I wanted to avoid having unnecessary "firings" of the state machine workflow.
    જવાબ ↓

જવાબ છોડો

તમારું ઇમેઇલ સરનામું પ્રકાશિત કરવામાં આવશે નહીં. જરૂરી ક્ષેત્રો ચિહ્નિત થયેલ છે *