UPDATE: I’ve been researching how to embed a SPD workflow into a site definition. Ovaj lanac MSDN forum ima neke zanimljive informacije. It’s not conclusive, ali ukazuje na put kroz džunglu.
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 … temperamentan.
Ljudi često pitaju / pitate / fretting over moving SPD workflows from one place to another. Danas, Pratio sam ove korake i napravio ove primjedbe:
- Sam stvorio tijek rada koristeći SharePoint Designer u mjestu povezan s biblioteci dokumenata.
- Povezanih biblioteka dokumenata već nalazi nekoliko dokumenata.
- Spasio sam mjesto kao predložak.
- Kad sam spasio mjesto kao predložak, Spasio sam sadržaj, kao i.
- I stvorio je novu stranicu u istoj zbirci web-mjesta koristeći da predložak.
U ovom trenutku, 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.
Nastavio sam:
- Otvoreno mjesto u SharePoint Designer.
- Had a peek at the workflow. It seemed fine.
- I clicked "Finish".
- Trčao sam tijek rada.
Ovaj puta, Internet izrađen prekid.
I’ll add that this workflow used the "collect data from user" radnja koja je relativno složen akcija pod haubom.
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.
Što to znači? 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, potpuno nove farme (e.g. dev, do stupnja da prod).
Ako ste čitajući ovo i skloni, molimo upisali komentar ili elektronička pošta mene your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.
</kraj>
