MEA cultur — SharePoint Designer * Dövlət Maşın axınları yarada

4 Cavablar

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, Mən rast gəldi Bu 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, lakin burada mahiyyət var:

  • Bu yanaşma bir iş siyahısı maddə dəyişə bilərsiniz ki, yararlanmaktadır, thereby triggering a new workflow. I’ve normally considered this to be a nuisance and even semaphores istifadə haqqında blogged onu idarə etmək.
  • SharePoint birdən çox müstəqil axınları xüsusi siyahı maddə qarşı fəal olmaq imkanı verir.

Bu konfiqurasiya:

  • Üçün dövlət Maşın Design (İ.E., dövlətlər və bir sonrakı necə dövlətlərin keçid).
  • Ayrı-ayrı iş kimi hər bir dövlətin həyata.
  • Siyahısı maddə hər hansı dəyişikliklərə cavab olaraq icra etmək bu dövlət axınları hər Yapılandır.

Hər bir dövlət iş bu kobud model aşağıdakı:

  • Başlatma sonra, determine whether it should really run by inspecting state information in the "current item". Abort if not.
  • Iş.
  • Update the "current item" with new state information. This triggers an update to the current item and fires off all the state workflows.

Bundan bir deklarativ dövlət maşın iş yarada bilər ki, aşkar fayda əldə, bütün dövlət informasiya bina KPIs və maraqlı views üçün dəhşətli deyil.

Bu kifayət qədər böyük günah yoxdur — standard workflow history tracking is even more useless than normal 🙂 That’s easily remedied, lakin. 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" Mən çünki, təəssüf ki,, 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.

</son>

Blog abunə.

Technorati Tags:

4 Haqqında "fikirləriMEA cultur — SharePoint Designer * Dövlət Maşın axınları yarada”

  1. Jaustral wrote:
    Salam Paul,
    how many states are you dealing with? I only get to have two different active workflows when I go to the workflow settings page?
    Yaxşı,
    Juan.
    Cavab ↓
  2. Sanjeev Rajput
    I’d really like to read the full examples. Hopefully one of you guys can help clarify some nightmares I’ve been having with my similar process. I’m at the point where I’m ready to start from fresh.
    Cavab ↓
  3. Paul 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, bu iş uzun sürən işidir çünki performans bir məsələ deyil (16 və ya həftə başa çatdırmaq üçün start) 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!
    –Paul G
    Cavab ↓
  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) iş. Lakin, the scope of what could be accomplished in this workflow is more limited that one would have with workflows for each state. Mən merak, lakin, what sort of performance hit takes place if all of the individual state workflows start up (albeit ending immediately thereafter).
    Həmçinin, 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, bir wait dövlət dilinə keçir, 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" dövlət maşın iş üzrə.
    Cavab ↓

Şəkil Yükləmə

E-poçt ünvanından dərc olunmayacaq. Lazım alanlar qeyd olunur *