Tim Bauer’s Running Thoughts

Semi-daily webcast summaries/insights

MSFT: WWF Overview

Watched this webcast today

Intro to WWF


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

June 26, 2006 Posted by bauertim | Uncategorized | , | No Comments

MSFT: WWF - Insider Sneak Peek

I watched this webcast (just for fun) today .. a quicky … with just 40 minutes in duration … 10 slides, 20 demo, 10 q&a.

Sneak Preview of WWF from an Early Adopters Perspective

It was definitely for the developers out there … 10 minutes of slides the rest of the time on code … and Q&A. From that here is my thoughts.

    1. Stable or not Stable … unclear The more I look at more trench level information on WCF it seems unstable at this time. The code examples they were providing seemed to be more rigid than flexible. Perhaps its just thier focus … definitely not synching w/ earlier demonstrations.
    2. I would grab thier code samples however … I would grab thier code samples … first time I have seen a different focus on the demo’s (versus building extensions off the same code base). They started from scratch … so could be a good baseline to review.

Here are my detail notes for those amused. Don’t go into withdrawls while I am on vacation (no posts from me next week on this stuff). [wink]

Quote:
Sneak Preview of WWF from an Early Adopters Perspective

Willy-Peter Schaub. BB&D MSFT Tech Unit. South Africa

…………..○ 1:00 - Agenda
……………………….§ WCF Overview
……………………….§ Perception
……………………….§ Roadmap
……………………….§ Demo
…………..○ Perception
……………………….§ Bad
……………………………………□ Code, feature, doc churn is high
……………………………………□ Lack of Integration w/ WCF GUI w/ VS is hard on admin
……………………………………□ X509 tricky
……………………………………□ 3rd interoperability on WS-*
……………………………………□ Currently lack of VSTS intg and WCF model artificats
……………………….§ Good
……………………………………□ SOA dev model is solid
……………………………………□ Abstraction and standard reduces code, complexity, and errors
……………………………………□ Unified dev model
………………………………………………..¨ Address, Binding, Contract is not an issue now
……………………………………□ Core infra
………………………………………………..¨ Distributed computing
………………………………………………..¨ Better performance (versus earlier releases)
…………..○ Roadmap
……………………….§ If you can use WCF … do
……………………….§ Target .NET 2.0
……………………………………□ If not use WSE2 or other tech
……………………….§ If WCF stable/released use it else use WSE 3.0 (good migration to WCF)
…………..○ 6:00 - Resources
……………………….§ www.saArchitects.net, www.saDevelopers.net
……………………….§ www.drop.co.za (Dev readiness program)
……………………….§ Presenters
……………………………………□ Willy@bbd.co.za, garret@bbd.co.za
……………………………………□ http://dotnet.org.za/willy
……………………………………□ http://dotnet.org.za/besserg
……………………………………□ Book2 - .NET Ent Solutions - Interoperability for the Connoiseur … IBN 0 620 34680 9
…………..○ 5:00 - Demo
……………………….§ Service and Data Contract definition
……………………….§ 10:00 - Create calculator service. (this is the demo a WWF based calc)
……………………….§ 11:30 - Define WWF configuration file (example on their website)
……………………….§ Right now WCF creates new instance on each call … so state is lost across calls … seo create session and sequence control code
……………………….§ Extend request/respond
……………………….§ Implement logic in calc service
……………………….§ Note, WCF bindings implement security so no need for further work
……………………….§ 19:00 Code focus is on transaction management through methods at this point
……………………….§ So calc service is now created
……………………….§ Now create client that consumes
……………………….§ Use cmd line to create a proxy via svcutil
……………………….§ Add proxy a linked file to client proj
……………………….§ Client callback defaults to port 80 …
……………………….§ The UI Is cmd line … (console)
……………………….§ Demonstrate error if methods in flow are out of sequence
…………..○ 29:00 - Q&A
……………………….§ Where get code?
……………………………………□ Uploading source code … to their site
……………………….§ What is instance context?
……………………….§ Online resources?
……………………………………□ SDK on WinFX
……………………….§ Request is what?
……………………………………□ Indigo objects. Serialized via SOAP. Could go to binary.
……………………….§ Ordering roles for 1st and Last, other way?
……………………………………□ No. 1st, last, svcs between. Otherwise sesion comes down.
……………………………………□ Configuration channel can assist in synch
……………………….§ Stateless … how inforced?
……………………………………□ First, Last, Intermediate works w/ stateless … still testing

June 10, 2006 Posted by bauertim | Uncategorized | , | No Comments

MSFT: BTS and WWF

Ah, now here was an example of a webcast where the summary and title sounded great but the horse flagged early in the race:

Integrating BizTalk Server 2006 and Windows Workflow Foundation

This guy was a MVP for MSFT on the BizTalk line and pointed to how they had built a $3M global system that had a plug and play forms model that business users did (basically where workflows or parts can be edited/added on the fly by the business). Unfortunately he didn’t show that too much … but did clearly have a deep DEEP grasp of BTS and WWF. He wandered around like a mad hatter at times.

Still there were keys:

    1. BTS Can’t Do the Hosted Rules Model? He didn’t talk to it but one of his slides alluded to it. In short WWF can allow rules to be done in a variety of places (and managed in there). This enables the business to use a tool of thier choice versus a howitzer tool like the BTS Rules Composer. A good reason to weave together BTS and WWF if true.

    2. WWF Can Scale Hosted By ASP.NET. Made an interesting point here that if the WWF process is loaded under ASP.NET it would inherit (as any webservice) alot of the scaling. He still feels if you are doing serious applications that BTS should step in for that role.

    3. WWF is not the silver bullet. He talked about how alot of shops are getting all warm and fuzzy over WWF and basing apps just on that. He thinks it is too early to say if what the SLA and performance of a WWF solution can be (still in beta). For now BTS should be leveraged and, if it helps, a plan to weave it out if WWF if POC’d at some point to handle the load well alone for a give app.

In short, an intersting deck … but not as cool as the name implies … here are my raw notes.

Quote:
MSDN Webcast: Integrating BizTalk Server 2006 and Windows Workflow Foundation (Level 200)

Pasted from <http://www.microsoft.com/events/webcasts/calendar/MonthView.aspx?audience=Developer>

Mike Badran - BTS MVP
Training & Integration Specialist, Breeze Training Pty Ltd
http://blogs.breezetraining.com.au/mickbv-mickba@microsoft.com

…………○ 1:00 — How BTS and WWF work together
……………………§ Use mgmt, framework, robust of bts 2006
……………………§ WWF for state based workflows and describe them in framework and then use the metadata from those flows in bts
…………○ 3:00 — Agenda
……………………§ $3M system demo that is a global system repository that leverages WWF and BTS
…………○ 4:30 — BTS 2006
……………………§ Robust, Scalable, Highly Avail
……………………§ BAM
……………………§ Solid Admin / Dev Tools
……………………§ Tried and Tested in mission critical
……………………§ Powerful rules engine
……………………§ Loves XML but will do any files format
……………………§ 6:30 — Their solution had the business uploading files and extending the system w/o intervention
…………○ 8:30 — WWF Overview
……………………§ Framework for describing a workflow
……………………§ Long running and stateful
……………………§ Access to lower levels of workflow runtime engine (lower that BizTalk)
……………………§ Host it somewhere (no server)
……………………§ Rules can be hosted … rules engine can look to XLS for example … highly requested feature (implied by slide NOT IN BTS not commented on but listed on slide)
……………………§ Can run 2000 rules at a time in BTS … but it is considerable less in WWF
……………………§ If sequence begins to fail (too complex for linear) move to state based
……………………§ State based is ‘code heavy’ at this time but less and less w/ each release
…………○ 20:00 — User Requirements for the $3M System they build (the demo)
……………………§ Hard to update existing forms (processing rules) .. Make easier
……………………§ Want users to create new forms in < 20/hrs (versus tech taking > 40/hr)
……………………§ Simple to implement for users
……………………§ Solution must scale
……………………§ Approach
………………………………□ Use BTS to manage forms processing (workflow process)
………………………………□ Use BTS for enterprise class
………………………………□ Use WWF for workflow plugable arch (where users change stuff)
…………………………………………¨ Could use BTS a little in workflow, WWF prime
…………………………………………¨ Could use BTS for prime, and WWF for small pieces
…………○ 25:30 - Put pieces together
……………………§ BTS
………………………………□ manage overall, validate msgs, promote properties
………………………………□ Long / short running processing
………………………………□ Exposure bts orchestrations as services
………………………………□ Use content based routing for flexible mgmt arch
…………………………………………¨ Use msg information (context) for routing, packet,
…………………………………………¨ Put filters on orchestrations …
…………………………………………¨ 3-4 milliseconds cost … run v2/v1 of forms at same time
………………………………□ Persistence of messages in BTS makes him feel safer (could do in WWF)
……………………§ WWF
………………………………□ Use State Based Workflows for rich workflow metadata
………………………………□ Articulate state transitions
………………………………□ Can pass typed information to workflow from application … create a reference to type of data … not loose binding … would req form library … use reflection via config info … WWF can do that
………………………………□ Host in?
…………………………………………¨ BTS as method call or as an adapter
…………………………………………¨ ASP.NET web service
……………………………………………………◊ Gives scale, cluster, load balanced
……………………………………………………◊ Persistence possible as normal
……………………………………………………◊ Set session timeouts to longest a workflow could run … since you store in the session object
……………………………………………………◊ BAD? … translate ASP.NET session ID to workflow ID … so you need to track / exhibit …
……………………§ Overall Solution
………………………………□ BTS
…………………………………………¨ Schema Validation, Property Extraction (fascade, form mgt)
…………………………………………¨ Central schema validation versus distributed in WWF
………………………………□ Workflow Services — Loader of workflow, specific workflows plugged in here
…………○ 41:00 - Demo
……………………§ In VS
………………………………□ Form Envelope / Container (not in Schema) … used to manage any form
………………………………□ Most important piece of info Form Type
………………………………□ Travel form to WorldCup
………………………………□ Look at XML returned by workflow
…………………………………………¨ Workflow ID key. WWF can take in that ID to trigger workflows
…………………………………………¨ Assembly (dll)
…………………………………………¨ Workflow Name
………………………………□ Look at orchestration for form
…………………………………………¨ Filters that allow Orchestration to pick up
………………………………□ Look at state workflow behind travel form. Based on Superstate. A derived class (to get workflow states to show on form).
………………………………□ Get Workflow Type from instance (get current state, or what are possible states, fantastic seperates workflow) … shows how to load form from reflection (vs hardcoding which wouldn’t allow plug and play). Available from his blog.
………………………………□ BTS - Rules Composer 2006
…………○ 57:20 - Resources
……………………§ Demos/slides: Http://blogs.breezetraining.com.au/mickb
…………○ 58:00 - Q&A
……………………§ K2.net positioning?
………………………………□ They are basing their codebase on WWF. Coding with it. In next release it will be based on WWF.
……………………§ Where Rules?
………………………………□ Simple rules in WWF and let business users have easier path. Not as scalable. BTS rules can scale better. Out of box w/ WWF you can put the rules anywhere. Samples on wwf.net for a central repository.
……………………§ WWF Price?
………………………………□ Free. Toolset. WinFX.
……………………§ Restart and Multi Thread WWF?
………………………………□ Yes. Tons of performance options. Use manual Workflow scheduler. Add to runtime prior to start. Internally in runtime there are queues. Actions get queued there. Then you kick the workflow … clears queue. Then it stops till next ‘run’ trigger.
……………………§ XLS leverage of rules.
………………………………□ Excel can do rules intg. Part of code brings into memory. On xls click evaluate. That comes back and says high/med/low based on rules outcomes.
……………………§ Books?
………………………………□ No. A lot of hype of WWF. A lot of people are saying use WWF for everything. But if they did there are scenarios where its 20,000 lines in WWF but 5 lines in BTS. Next slice of BTS will have WWF designer and WWF Adapter … (around 2007 or 2008?). R2. Performance is a big unknown right now. In beta. Always going through intermediary … pass to via runtime.

June 6, 2006 Posted by bauertim | Uncategorized | , , | No Comments

MSFT: WWF - Primer

Watched this webcast today (still gearing on a specific estimate for a client that heavily involves workflow)

Getting Up To Speed with Windows Workflow Foundation (Level 200)

Interesting point I only watched it because it wanted to watch something while I ran. Turns out that a ton of insights came out of it (seems MSFT is gearing up on this topic as well - getting more robust examples each week).

    1. Visual Designer (can be hosted outside of VS). Bingo. This is what I have been looking for. The ability for end users to not have to go into VS to edit workflows. They showed a sample application that can allow a user to edit specific areas of workflows defined in VS. Take that and add some G&R/FC special sauce and you have something pretty cool (think similar to ECM templates and global regions couples w/ user definable areas on a website - now think process flow). Huzzah!

    2. Sneaky MSFT or shall I say Brillant. It also became evident on what thier angle is on bundling / offering all this power on workflow/rules for free (in effect) to developers. Get the applications hooked on this style of construct and then let the applications dictate when the BizTalk server is needed to support applications that flounder hosting the workflow services on thier own. Brillant.

    3. Free Workflow Monitor. They showed a sample application that allows a workflow manager to (1) select a workflow (2) see the history of threads that have gone through it or active ones and (3) drill into one historical thread and see why it pathed the way it did. Huzzah again. More special sauce and you have a nice workflow manager dashboard + a customer service troubleshooting tool (why did transaction xyz process the way it did).

Man … talk about lucking out. I assume that there will be subsequent webcasts that drill into the examples above (typical MSFT style) but this one is definitely worth watching … for the technical and business sides.

Here are my detail notes:

Quote:
MSDN Webcast: Getting Up To Speed with Windows Workflow Foundation (Level 200)

Pasted from <http://www.microsoft.com/events/webcasts/calendar/MonthView.aspx?audience=Developer>

…………○ 1:00 - Agenda
…………○ 2:00 - What is a Workflow
……………………§ Coordinations of People and Software
……………………§ Like a flowchart (sequential diagram … good for workflows that are know flows simple) or diagram (state machine / diagram … adhoc workflow)
……………………§ Rules Engine. Complex rules to get a credit score, pricing. It is a workflow since the rules are organized in a similar structure.
…………○ 5:00 - Arch
……………………§ Part of WinFX
……………………§ Set of Assemblies
……………………§ Needs to be hosted in another process (exe, iis, SP server, etc)
……………………§ Components
………………………………□ Base Activity Library
………………………………□ Runtime Engine
………………………………□ Runtime Services
………………………………□ Visual Designer (can be hosted outside of VS)
…………○ 9:36 - Activity Arch
……………………§ Fundamental Building Blocks
……………………§ Composite Activities
……………………§ Extendable (especially activities)
………………………………□ Composition (assemble of other activities)
………………………………□ Author new ones
………………………………□ Extend existing ones
………………………………□ Build Activity Libraries for domains (compliance, crm, rosetta, etc)
…………○ 13:30 - Runtime Extensions
……………………§ Persistence Service (allows workflows to sleep - out of mem)
………………………………□ Default is Writing to SQLServer could go to file
……………………§ Tracking Service (manages profiles and tracked info)
……………………§ Scheduler Service (threads, timers, transactions)
……………………§ [bauer comment: strategy is WWF is the loss leader. Get them using the workflow / rules power then realize it can't run embedded well. Require upgrade to BizTalk Server. Brillant]
…………○ 20:00 - Demo (types, out of box, host interaction, conditional logic, etc)
……………………§ Add code activity.
………………………………□ Smart tags on object saying what needs to be set
……………………§ Show how host application holds workflow
……………………§ Show pass in of parm to workflow.
………………………………□ Create property on workflow class
………………………………□ Adjust workflow call to pass in (use hash table)
……………………§ Add if/then/else condition and show rules designer
……………………§ Create Activity by Composition
………………………………□ Drop code activity, sequential component, etc
………………………………□ Can see composition in fulll or roll up
…………○ 33:00 - Scenarios
……………………§ Focus on long running process
……………………§ Complex rules
……………………§ AdhocWorkflows
……………………§ Customizing in flight
……………………§ Surface process info to users
……………………§ Allow users to customize
…………○ 34:00 - Demo
……………………§ Long running process
………………………………□ Oob - Timeouts, persist out of memory
………………………………□ Expense report process - submit, approvals (auto vs manual),
………………………………□ 3 apps - submit, mgr review / approve, host (listen/exec wwf on msdn)
………………………………□ RuleSet - Have that policy executed to drive values that workflow uses to run
………………………………□ Host process is done a variety of ways
……………………§ Rules functionality in workflow
………………………………¨ Example of a form where all events are handle by workflow snippets. The form application doesn’t know anything about what is going on.
………………………………¨ All the app does is exec rules (2-3 lines of code)
………………………………¨ RuleSet are stored in DB. Exposed via designer. Think of them acting against objects in workflow BUT could be acting against the form. Rule Engine handles complex forward chains.
……………………§ Ad Hoc - Human Workflows - Use State Machine
………………………………¨ IVR. Based on State set values. State set by pathing of usiner
………………………………¨ Each prompt is a state in state machine
……………………§ Surfacing Workflow Information
………………………………□ Sample in SDK (workflow monitor)
…………………………………………¨ See threads (history) that have gone through
…………………………………………¨ See detail steps in each thread (history)
…………………………………………¨ This is not VS based
…………………………………………¨ Allows for good information on what is in process
……………………§ Allow Users to Customize Process
………………………………□ Allow users to put specific activities into specific points in workflow
………………………………□ Via a non VS based GUI
………………………………□ Save to XOML
………………………………□ View XOML. MSDN Search Activity
………………………………□ Not clear if its possible to set values of activities
…………○ 53:00 - QA
……………………§ Links for WCF?
……………………§ Bug in ASP.NET for waking up slumbering process (beta 2.2). He points to a blog.
……………………§ Host image of process external? Yes, can save to BMP. Get that file out. John Flander’s blog has a good example of that.
……………………§ Host WWF application on Webservice? Yes
……………………§ Design Shell Source Code? Yes on WWF.net later today
……………………§ SQL Server Svc Broker Use This? No. Six products in development using WWF. Office, Biztalk, MSFT Dynamics. Paul Anders Blog talks about that.
……………………§ Latest Version? Beta 2. WWF.Net has that.
……………………§ Replace BizTalk Orchestration? No. BTS is a full featured platform. Could build a lot of it in WWF. BTS has adapters, mgmt, distributed hosts, etc.
……………………§ Is XOML simliar to XAML? Same thing … just named to allow VS to open it.

June 2, 2006 Posted by bauertim | Uncategorized | , , , | No Comments

MSFT: WWF - Rules Based Apps

Watched this webcast today:

Building Rules-Based Applications Using Windows Workflow Foundation (Level 200)

As we continue to get a good grasp of what is possible with workflow options in the solution delivery area. Clients are continuing to assess how workflow and rules engines can make thier work easier. However, we have found that most implement before having a stable basis and then require intervention … let’s avoid that.

The key points I heard came at 48 minutes in:

    1. Patience. Patience is key is lesson #1. As I listened to the first part it was interesting but not ‘ah ha’ material. 48 minutes later however, when they started tinkering around with how the rules engine can be exposed to end users … lesson? Patience … there is always insight … smart people take awhile getting to it sometimes.

    2. Rules Editable By End Users. They showed examples of how the rule set and the native rules editor can be exposed out to the user base. Very nice.

    3. Rules Can Be Live Immediately. Users can edit in thier tools and see the next transaction processed differently (no recompile, no assembly tinkering, just done).

I am still pondering the implications of CAG, Policies, and forward chaining … So if someone wants to vett that out for me feel free. It also continues to elude me on the specific differences between BizTalk and WWF outside of you don’t need to embed it in the application among other infra points. So more clarity there is required.

Here are my detail notes for those interested:

Quote:
Building Rules-Based Applications Using Windows Workflow Foundation (Level 200)

Pasted from <http://www.microsoft.com/events/webcasts/calendar/MonthView.aspx?stdate=4/1/2006&audience=Developer&series=Business%20Process%20Integration:%20Integrate%20Workflow,%20Messaging,%20and%20Services&product=0&presenter=0&tz=0>

Rules can be powerful business tools when combined with workflow. This webcast examines the rules engine capabilities in Windows Workflow Foundation, and shows how you can use rules to drive workflow execution. Learn how rule policies facilitate the description of sophisticated behavior in an integrated and flexible way. We also discuss the extensibility mechanisms in Windows Workflow Foundation that enable you to leverage the rules engine in any Microsoft .NET-connected application.
Presenter: Jurgen Willis, Program Manager, Microsoft Corporation

Pasted from <http://www.microsoft.com/events/EventDetails.aspx?CMTYSvcSource=MSCOMMedia&Params=%7eCMTYDataSvcParams%5e%7earg+Name%3d%22ID%22+Value%3d%221032293933%22%2f%5e%7earg+Name%3d%22ProviderID%22+Value%3d%22A6B43178-497C-4225-BA42-DF595171F04C%22%2f%5e%7earg+Name%3d%22lang%22+Value%3d%22en%22%2f%5e%7earg+Name%3d%22cr%22+Value%3d%22US%22%2f%5e%7esParams%5e%7e%2fsParams%5e%7e%2fCMTYDataSvcParams%5e>

Jurgen Willis . Program Mgr (MSFT) on WWF Team
…………○ 1:00 Overview
……………………§ Long Running Stateful
……………………§ Flexible Flow
……………………§ Business Logic Transparency
……………………§ Visual Designer
……………………§ Host Process: Service, Engine, Activity Library
……………………§ In WinFX and O12
……………………§ Custom Activities and Base Activity Lib
…………○ WWF = Rules Engine
…………○ 6:00 - Workflow Rules
……………………§ 4 out of box activities
………………………………□ If/Else
………………………………□ While
………………………………□ Replicator
………………………………□ Conditioned Activity Group (CAG)
………………………………□ (CUSTOM Activities You Build)
……………………§ Forward Chaining Rules
……………………§ Rules can be used outside of workflow
…………○ 8:00 - Demo 1 - Build Travel Book App
……………………§ Create runtime (can execute in Windows Form)
……………………§ This one will support a form
……………………§ Show If/Else and How Objects Maps to Methods
……………………§ Condition could be code in properties of condition box … or launch condition edition editor … code like field for evaluting condition expression … generates a xml ‘rules’ file
……………………§ Use declarative rules to enable add / remove rules on running process …
…………○ 17:30 - Conditioned Activity Group (CAG)
……………………§ Controls sequence of activities
……………………§ Collaborative activities sequence can be determined via CAG (like order approve)
……………………§ Default CAG = When (once) + Until (all children done and when == false)
……………………§ Can do custom Until (override CAG waiting for children) … no new activities, cancelled blocked activities
…………○ 22:30 - Demo of CAG
……………………§ Could do what CAG does w/ multiple listeners … but this simplifies
…………○ 26:30 - Policy Activity
……………………§ Activity that references a rule set (.rules file)
……………………§ If/then/else expressions that eval op and workflow members
……………………§ Future BizTalk will build on WWF
…………○ 29:00 - Demo of Policy
…………○ 31:00 - Forward Chaining
……………………§ Implicit dependencies between rules (set a field used in a 2nd rule eval)
……………………§ Example
………………………………□ If < 100 disc = 10%
………………………………□ If > 100 disc = 15%
………………………………□ If amt > 0 total = total + disc
………………………………□ Will execute 1, 3, 2
……………………§ Priority value can be used to order rule eval
……………………§ Chain on 3 diff things
………………………………Implicit (based on property usage)
………………………………□ Explicit
………………………………□ Partially Explicit (attributes on method, ruleread,rulewrite, ruleinvoke)
……………………§ Limit Chaining
………………………………□ Halt, RuleSet Chaining Behavior (full, explicit, none), ReEvaluation (always, never)
…………○ 37:30 - Externalizing Rules
……………………§ RuleSets stored in DB example
……………………§ Define a custom policy activity
……………………§ GetRuleSet method
……………………§ When execute policy .. Gets handle on ruleset service that calls get ruleset svc … do exec of service …
……………………§ Default RuleSet Editor … versions available … editors can be used outside of VS (KEY POINT)
……………………§ Can define workflows to pickup latest version of RuleSet or use a specific version
……………………§ No recompile or touching of assemblies
…………○ 45:00 - Rules Extensionability
……………………§ Manage rules from workflow
……………………§ Create custom activities
……………………§ Re-use editors in VS outside
……………………§ Create a custom tool for authoring rules (use objects of rules editor to create custom editor)
……………………§ Leverage rules from any MSFT .NET application
…………○ 47:00 - Summary
……………………§ Integrated rules and workflow
……………………§ Rules engine flexible around forward chaining
……………………§ Combination of rules … control of workflow definition
……………………§ Many rules out of box
…………○ 48:30 — Resources
……………………§ SDK Samples
………………………………□ IfElse
………………………………□ Changing Rules dynamic update
………………………………□ Simple and Advanced Policies
………………………………□ Tracking Event Sample
……………………§ http://windowsworkflow.net
………………………………□ Travel demo
………………………………□ External ruleset toolkit
………………………………□ Rules in excel (ops against ruleset)
………………………………□ RuleSet Analyzer
……………………§ MSDN Article http://msdn.microsoft.com/workflow
………………………………□ Introduction to WWF Rules
………………………………□ Couple new points
…………○ 51:00 — Q&A
……………………§ Where did CAG come from? Goal combine workflow (model) and rules. In sequential and state workflow … so workflow needs a flexibility point … CAG.
……………………§ Rules can execute other rulesets (custom rule action)

May 30, 2006 Posted by bauertim | Uncategorized | , | No Comments