MSFT: WWF Overview
Watched this webcast today
Not so much as it was new material but I was curious on if the message had matured since earlier (intro to WWF webcasts). It had a bit. The keys I took away were
1. Good Overview Slides. Had two good overview slides that I captured for you (see below). One on Biztalk vs WWF. The other on base execution view.
2. Domain Specific Activities. Its interesting that the Domain Specific Activities might be a way to seperate ourselves from the pack. For example, our investment in Patient Intelligence Registry (BI Play) will have Domain specific workflows (or could). Nice way to extend that play (as we are right now trying to build a Sharepoint front end based on Business Data Catalogue).
3. State. It’s interesting that this time around I began to think our messaging should be around state. Sequential is in there (granted). But state can be the forest business layer that triggers sequential flows when appropriate.
Detail notes are below:
| Quote: |
| Gerald Walsh. Developer Evangelist. Introduction to WWF (100) …………..○ 1:30 - Agenda ……………………….§ Intro ……………………….§ Integration ……………………….§ Workflow basics ……………………….§ Building a workflow ……………………….§ Activities ……………………….§ Execution and Control Flow ……………………….§ Workflow design tools ……………………….§ Integration w/ Office ……………………….§ Summary ……………………….§ Resources …………..○ What is a workflow? Activities to coordinate people and/or software. …………..○ Two categories ……………………….§ Flow chart ……………………….§ State diagram (less transactional, more human) …………..○ 4:30 Challenges ……………………….§ Long running & Stateful ……………………….§ Flexible control flow ……………………….§ Transparency …………..○ Release ……………………….§ Beta 2.2 ……………………………………□ WinFX dropped ……………………………………□ Launced in .NET 3.0 (put in WCF, WWF, WPF, etc) …………..○ BizTalk vs WWF ……………………….§ BizTalk superset of WWF ……………………………………□ …………..○ 10:30 - WWF ……………………….§ Compiled DLL (reside in host process) ……………………….§ Workflow, Activity Library, Workflow Runtime Engine, Runtime Services (state mgmt, persistance, tracking, timer svcs, transaction svcs, intfc for custom run time svcs) ……………………….§ Interfaces to work on workflow ……………………………………□ Sharepoint Designer (Frontpage next release) ……………………………………□ VS 2005 plug in …………..○ 15:00 - 2 ways to define ……………………….§ Code ……………………….§ Markup (XML). Nice (enables the external app definition of a workflow) …………..○ 17:00 - Demo ……………………….§ 17:30 - 2 types of projects ……………………………………□ Console (prog file to allow run in console file) ……………………………………□ Workflow library (where you have a host) ……………………….§ Review of Activities that could be done in workflow (part of VS2005) ……………………….§ 25:30 - End demo (shows console firing up, msg, and closing) …………..○ 26:00 - Authoring Modes ……………………….§ XAML only ……………………….§ XAML and Code ……………………….§ Code Only ……………………….§ Application Generated …………..○ 28:00 - Activities Basics ……………………….§ Activities Building Blocks of Workflows ……………………….§ Activities are Classes ……………………………………□ Base ……………………………………□ Custom Activities ………………………………………………..¨ Compose Activities (aggregate) ………………………………………………..¨ Extend ………………………………………………..¨ Author New ……………………………………□ Domain Specific Workflow Packages ………………………………………………..¨ Opp for GR/FC? …………..○ 33:30 - Workflow Execution ……………………….§ ……………………….§ 35:30 - Dehydrate / Rehydrate the workflow (where the workflow is saved to disk after inactivity) …………..○ 37:00 - Flexible Control Flow ……………………….§ Sequential (flowchart) ……………………….§ State Machine ……………………………………□ setup external comm ……………………………………□ Event drive (host is beefier) ……………………….§ Rules Driven ……………………………………□ Complex policies ……………………………………□ CAG (Constrained Activity Group) is key foundation …………..○ 39:00 - State Demo ……………………….§ 43:30 - Bumbling around. ……………………….§ Couldn’t link the states (in GUI) … DOH! …………..○ 45:00 - Taking Workflow Mainstream ……………………….§ Design - VS 2005 ……………………………………□ Sequential Designer ……………………….□ State Machine Designer ……………………………………□ Activity Designer ……………………….§ Office ……………………………………□ Sharepoint Server manages workflow typically (outlook can be a client using VB tools for office) ……………………………………□ Example, invoice in word, save to sharepoint, trigger workflow, etc ……………………………………□ Sharepoint Designer allows non-tech to design workflows (employee tracking, invoice tracking, etc) …………..○ 53:00 - Q&A ……………………….§ Remoting ……………………….§ Nothing else notable |
Subscribe