This blog entry is more of an "in the realm of the possible" dħul vs. info konkreti.
We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Bażikament, users enter data into a "new customer" lista tad-dwana u mbagħad meta jkunu lesti u vvalidati l-proċess dħul tad-data, għandna bżonn li jinħoloq sit għall dak il-klijent.
Jien kemm big fan ta 'workflow dikjarattiva kif ukoll viżwali programmer dgħajfa workflow studio, hekk jien ridt li jilħqu l-ħtieġa li jużaw SharePoint Designer.
I pjan biex jiktbu dwar dan f'aktar dettall (u nisperaw preżenti għal grupp ta 'utenti jew tnejn fis-sena li ġejja), iżda hawnhekk huwa l-soluzzjoni ġenerali:
- Oħloq azzjoni drawwa li jintegra ma SPD.
- L-azzjoni tad-dwana tippermetti SPD li tinvoka servizz web u tgħaddih sensiela ta 'XML.
- Locates servizz web tal-ringiela fil-lista tad-dwana u toħloq sit ġdid bħala per-data għal dak klijent ġdid bl-użu ta 'definizzjoni sit custom.
- Web servizz imbagħad jaġġorna l-lista tad-dwana ma 'xi informazzjoni bħal link għas-sit il-ġdid.
Aħna kkunsidrati approċċi oħra, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, hemm ħafna ta 'C # kodiċi f'din is-soluzzjoni, imma hija mgeżwra ġewwa workflow dikjarattiva, hekk aħna nikseb xi wħud mill-benefiċċji ta 'workflow dikjarattiva filwaqt hooking fis-servizz tal-ħolqien tal site.
All we need now is an easy tool to automatically migrate SPD workflows around as easily as we can for visual studio workflows and we’ll really be cooking with gas 🙂 I understand that some folk are out there working on this problem and I hope they have some good success with it soon.
</aħħar>
